| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, Jaime Casanova <systemguards(at)gmail(dot)com>, Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: index row size exceeds btree maximum, 2713 - |
| Date: | 2005-07-19 15:25:52 |
| Message-ID: | 24837.1121786752@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:
> On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
>> You can index text fields, but you can't insert values bigger then
>> BLOCKSIZE/3 when you have an index on that column.]
> Please note that the size limitation is for btree indexes, the most
> common and well tested index types.
> For hash you can have a much larger value, but only direct matching is
> supported.
> I don't know about GiST...
None of the index types support entries larger than BLOCKSIZE-less-a-bit,
so switching to a different index type won't do more than push the
problem out by a factor of about 3.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samuel Thoraval | 2005-07-19 15:36:35 | Re: Hot to restrict access to subset of data |
| Previous Message | Tom Lane | 2005-07-19 15:22:58 | Re: Hot to restrict access to subset of data |