phpwiki-talk

[Phpwiki-talk] page too big

[Didier B. <db...@in...>]

Hello,

  I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
the error:

Warning: PostgreSQL query failed: ERROR: Tuple is too big: size 8152, max size 8140 in
/mnt/commun/local/phpwiki-1.2.0/lib/pgsql.php on line 145
Insert/update failed: ERROR: Tuple is too big: size 8152, max size 8140

How can I do to empty this page ?

Thanks.

Regards.
-- 
            .------------------------------------------------.
    .^.     | Didier Bretin, France | db...@in...    |
    /V\     |-----------------------| www.informactis.com    |
   // \\    |                       `------------------------|
  /(   )\   | Visit: http://www.fnh.org/                     |
   ^^-^^    `------------------------------------------------'

Re: [Phpwiki-talk] page too big

[Reini U. <ru...@x-...>]

click on EditText

Didier Bretin schrieb:
>   I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
> the error:
> How can I do to empty this page ?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] page too big

[Steve W. <sw...@pa...>]

On Thu, 19 Apr 2001, Reini Urban wrote:

> click on EditText

Also, I think you've run into a problem with Postgresql that's been around
a long time. From the INSTALL.pgsql:

"Also note that Postgresql by default has a hard limit of 8K per
row. This is a Really Bad Thing. You can change that when you compile
Postgresql to allow 32K per row, but supposedly performance
suffers. The 7.x release of Postgresql is supposed to fix this."

~swain

>
> Didier Bretin schrieb:
> >   I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
> > the error:
> > How can I do to empty this page ?
> --
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

Re: [Phpwiki-talk] page too big

[Didier B. <db...@in...>]

Hello,

On Thu, Apr 19, 2001 at 09:17:56PM -0400, Steve Wainstead wrote:
> On Thu, 19 Apr 2001, Reini Urban wrote:
> 
> > click on EditText
Oops :o). I thought that I can't do this because it is a generated page.
So I do it :o)))

> Also, I think you've run into a problem with Postgresql that's been around
> a long time. From the INSTALL.pgsql:
> 
> "Also note that Postgresql by default has a hard limit of 8K per
> row. This is a Really Bad Thing. You can change that when you compile
> Postgresql to allow 32K per row, but supposedly performance
> suffers. The 7.x release of Postgresql is supposed to fix this."
Ok :o).
Apparently I'm with a 7.x release ... so the problem is not resolve
in Postgres .... Hummmm...... I will search at Postgres 's site.

Thanks.

-- 
            .------------------------------------------------.
    .^.     | Didier Bretin, France | db...@in...    |
    /V\     |-----------------------| www.informactis.com    |
   // \\    |                       `------------------------|
  /(   )\   | Visit: http://www.fnh.org/                     |
   ^^-^^    `------------------------------------------------'

Re: [Phpwiki-talk] page too big

[Sandino A. <sa...@sa...>]

Didier Bretin wrote:

> Hello,
>
> On Thu, Apr 19, 2001 at 09:17:56PM -0400, Steve Wainstead wrote:
> > On Thu, 19 Apr 2001, Reini Urban wrote:
> >
> > > click on EditText
> Oops :o). I thought that I can't do this because it is a generated page.
> So I do it :o)))
>
> > Also, I think you've run into a problem with Postgresql that's been a=
round
> > a long time. From the INSTALL.pgsql:
> >
> > "Also note that Postgresql by default has a hard limit of 8K per
> > row. This is a Really Bad Thing. You can change that when you compile
> > Postgresql to allow 32K per row, but supposedly performance
> > suffers. The 7.x release of Postgresql is supposed to fix this."
> Ok :o).
> Apparently I'm with a 7.x release ... so the problem is not resolve
> in Postgres .... Hummmm...... I will search at Postgres 's site.
>

The problem is supposed to be resolved in 7.3.

--
Sandino Araico S=E1nchez
Si no eres parte de la soluci=F3n, entonces eres parte del precipitado.