Trying to use GIST indexes again

[Greg Stark]

What does this mean?

test=> create index cache_i_gist_sl on cache using gist (r_id, sl_ids);
ERROR: index row requires 8216 bytes, maximum size is 8191

Postgres 7.4.2
I have btree_gist and intarray loaded.
r_id is an integer, sl_ids is an int[].

Does it simply mean one of the int arrays is too large? Most of them have 0,
1, or 2, but there are the occasional entries with up to 2,141 elements.

--
greg
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Alvaro Herrera]

On Tue, Aug 03, 2004 at 11:05:28AM -0400, Greg Stark wrote:

test=> create index cache_i_gist_sl on cache using gist (r_id, sl_ids);
ERROR: index row requires 8216 bytes, maximum size is 8191

Postgres 7.4.2
I have btree_gist and intarray loaded.
r_id is an integer, sl_ids is an int[].

Does it simply mean one of the int arrays is too large? Most of them have 0,
1, or 2, but there are the occasional entries with up to 2,141 elements.

Yes. Probably you could work around that by using a larger BLCKSZ ...

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
One man's impedance mismatch is another man's layer of abstraction.
(Lincoln Yeoh)
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html