Re: BUG #12292: index row size 1480 exceeds maximum 1352 for index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: robert(dot)thaler(at)cellent(dot)at
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12292: index row size 1480 exceeds maximum 1352 for index
Date: 2014-12-21 18:39:39
Message-ID: 2275.1419187179@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

robert(dot)thaler(at)cellent(dot)at writes:
> I tried to upgrade from postgres 9.3.5 and imported a database export
> created by pg_dump. the import shows the following error:
> ERROR: index row size 1480 exceeds
> maximum 1352 for index "idx_sm_post_content"

> manually creating the gin index for fulltext search does not work too and
> produces the same error.

> create index idx_sm_post_content
> on client.sm_post using gin (to_tsvector('english', "content"))

> on postgres 9.3.5 creating the index on the same data works fine.

Hm, can you provide sample data that triggers this? The GIN code
looks like it's supposed to avoid this limit at higher logic levels,
but evidently that's dropping the ball somewhere. Hard to tell where
without a concrete example though.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-12-22 00:48:51 Re: BUG #12300: ~/.psql_history nonexistent warning on first run
Previous Message alex 2014-12-21 16:31:52 Re: segfault on query