Re: SIGSEGV in BRIN autosummarize

On Wed, Oct 18, 2017 at 07:22:27PM +0200, Alvaro Herrera wrote:
> Do you still have those core dumps? If so, would you please verify the
> database that autovacuum was running in? Just open each with gdb (using
> the original postgres binary, not the one you just installed) and do
> "print MyDatabaseId".

[pryzbyj(at)database ~]$ gdb ccpp-2017-10-16-23:21:22-31543/coredump -ex 'p MyDatabaseId' -ex q 2>/dev/null |tail -5
Core was generated by `postgres: autovacuum worker process gtt '.
Program terminated with signal 11, Segmentation fault.
#0 index_close (relation=0x324647603246466, lockmode=1) at indexam.c:178
178 LockRelId relid = relation->rd_lockInfo.lockRelId;
$1 = 16400

[pryzbyj(at)database ~]$ gdb ccpp-2017-10-14-18:05:35-26500/coredump -ex 'p MyDatabaseId' -ex q 2>/dev/null |tail -5
Core was generated by `postgres: autovacuum worker process gtt '.
Program terminated with signal 11, Segmentation fault.
#0 pfree (pointer=0x298c740) at mcxt.c:954
954 (*context->methods->free_p) (context, pointer);
$1 = 16400

gtt=# SELECT oid,datname FROM pg_database;
13456 | template0
16400 | gtt
13457 | postgres
1 | template1

The gtt DB is where the (only) BRIN indicies are (not sure what to conclude
from that?)

Justin