From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [sqlsmith] PANIC: failed to add BRIN tuple |
Date: | 2016-05-24 23:13:04 |
Message-ID: | 20160524231304.GA471539@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Seltenreich wrote:
> There was one instance of this PANIC when testing with the regression db
> of master at 50e5315.
>
> ,----
> | WARNING: specified item offset is too large
> | PANIC: failed to add BRIN tuple
> | server closed the connection unexpectedly
> `----
>
> It is reproducible with the query below on this instance only. I've put
> the data directory (20MB) here:
>
> http://ansel.ydns.eu/~andreas/brincrash.tar.xz
>
> The instance was running on Debian Jessie amd64. Query and Backtrace
> below.
How long does it take for you to reproduce this panic in the unpatched
code? This patch fixes the immediate problem, but it'd be good if the
bug is fixed more generally.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
brincrash.patch | text/x-diff | 4.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Seltenreich | 2016-05-24 23:40:49 | Re: [sqlsmith] PANIC: failed to add BRIN tuple |
Previous Message | Tom Lane | 2016-05-24 22:56:32 | Re: To-Do item: skip table scan for adding column with provable check constraints |