Unusable SP-GiST index

From: Vik Fearing <vik(at)2ndquadrant(dot)fr>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Unusable SP-GiST index
Date: 2016-12-30 22:04:33
Message-ID: 49527f79-530d-0bfe-3dad-d183596afa92@2ndquadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

While trying to find a case where spgist wins over btree for text, I
came across the following behavior which I would consider a bug:

CREATE TABLE texts (value text);
INSERT INTO texts SELECT repeat('a', (2^20)::integer);
CREATE INDEX ON texts USING spgist (value);
SET enable_seqscan = off;
TABLE texts;

That produces:

ERROR: index row requires 12024 bytes, maximum size is 8191

It seems to me the index should not be allowed to be created if it won't
be usable.
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support


Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2016-12-30 22:07:56 Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal
Previous Message Alvaro Herrera 2016-12-30 19:56:52 Re: rewrite HeapSatisfiesHOTAndKey