| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | AW: [HACKERS] Error "vacuum pg_proc" |
| Date: | 1999-12-27 09:40:51 |
| Message-ID: | 219F68D65015D011A8E000006F8590C603FDC1E0@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Robinson | 1999-12-27 11:35:52 | Re: [HACKERS] database replication |
| Previous Message | Hannu Krosing | 1999-12-27 09:10:00 | Re: [HACKERS] database replication |