Andreas Seltenreich wrote:
> Alvaro Herrera writes:
>
> > If you can re-run sqlsmith and see if you can find different bugs, I'd
> > appreciate it.
> [...]
> > [2. text/x-diff; brincrash-2.patch]
>
> BRIN is inconspicuous since applying this patch. All coredumps I see
> now are either due to
Alvaro Herrera writes:
> If you can re-run sqlsmith and see if you can find different bugs, I'd
> appreciate it.
[...]
> [2. text/x-diff; brincrash-2.patch]
BRIN is inconspicuous since applying this patch. All coredumps I see
now are either due to the parallel worker shutdown issue or acl.c's
Andreas Seltenreich wrote:
> I wrote:
>
> > Re-fuzzing now with your patch applied.
>
> This so far yielded three BRIN core dumps on different machines with the
> same backtraces. Crash recovery fails in these cases.
>
> I've put the data directory here (before recovery):
>
>
I wrote:
> Re-fuzzing now with your patch applied.
This so far yielded three BRIN core dumps on different machines with the
same backtraces. Crash recovery fails in these cases.
I've put the data directory here (before recovery):
http://ansel.ydns.eu/~andreas/brincrash2-spidew.tar.xz
I wrote:
> Alvaro Herrera writes:
>> How long does it take for you to reproduce this panic in the unpatched
>> code?
>
> I could probably speed it up by creating lots of additional BRIN indexes
> in the regression database, and by compiling a sqlsmith that generates
> update statements only.
This
Alvaro Herrera writes:
> How long does it take for you to reproduce this panic in the unpatched
> code?
Very long, I'm afraid. I only observed it once, and according to the
logging database, about 4e9 random queries were generated since testing
with 9.5 code.
I could probably speed it up by
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
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
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
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.
10 matches
Mail list logo