From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | martin(dot)kevin(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: BUG #13461: Error message appears to use incorrect values |
Date: | 2015-06-22 21:20:05 |
Message-ID: | 24934.1435008005@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
martin(dot)kevin(at)gmail(dot)com writes:
> The following bug has been logged on the website:
> Bug reference: 13461
> Logged by: Kevin Martin
> Email address: martin(dot)kevin(at)gmail(dot)com
> PostgreSQL version: 9.4.1
> Operating system: AWS RDS
> Description:
> Given a column of 1000-dimension cubes the following triggers an error:
> CREATE INDEX ktest ON items USING gist(embeddings);
> ERROR: index row size 8016 exceeds maximum 8152 for index "ktest"
> The error message appears to be out of order - the index row size reported
> is smaller than the maximum.
Hm. No, the arguments are correctly ordered. What this looks like is the
criterion to throw the error is overly conservative, or maybe there's some
other logic bug in the page-split code. Can you supply sample data that
triggers this error?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-06-22 22:25:03 | Re: BUG #13459: Replaying WAL logs can hang on startup |
Previous Message | socketpair | 2015-06-22 20:34:11 | BUG #13462: Impossible to use COPY FORMAT BINARY in chunks through libpq |