AW: [HACKERS] Error "vacuum pg_proc" - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: [HACKERS] Error "vacuum pg_proc"
Date
Msg-id 219F68D65015D011A8E000006F8590C603FDC1E0@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> > It turns out that for an index on a single text column, the maximum
> > safe text length is 2700 bytes.  So the correct check for dangerous
> > procedure definitions in 6.5.* is
> 
> This is another argument to try and get long tuples into 7.0.

The limit of 2700 is btree specific, and imho a more than actually  
reasonable limit for a btree key.
Anybody wanting an index on a larger key would usually be 
better off with different indexing methods, like a functional
btree, hash, or text index.

Andreas


pgsql-hackers by date:

Previous
From: "Ansley, Michael"
Date:
Subject: Unlimited query length - the final chapter (aka pg_dump)
Next
From: Michael Robinson
Date:
Subject: Re: [HACKERS] database replication