> I've encountered a strange behavior of the VACUUM ANALYZE command.
> It seems that this command works only if the size of a text field
> does not exceed approximately 4050 bytes! So the real limit on
> tuple size is a half of the max tuple size. I've checked this effect
> on Postgres 6.4.2 (Sparc Solaris 2.5.1) and Postgres 6.5 (SUSE 6.1
> Linux, kernel 2.2.5). Is this a bug or known feature?
> The python script used to reproduce this problem and results for
> v6.4.2 and v6.5 are follows.
> size= 4059
> size= 4060
> size= 4061
> size= 4062
> size= 4063
> size= 4064
> size= 4065
> ERROR: Tuple is too big: size 8188
I have always suspected these default values where wrong, but no one
reported it as a bug.
Here is a patch for 6.5 which will prevent the creation of these too big
tuples in certain cases. Seems we should also check for max length at
the time we create the table, but it doesn't look like there is any code
to do that yet.
I am not going to apply this to 6.5.1 because it may have some unknown
side-affects.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026