pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Thu, 1 Nov 2018 16:51:49 +0100
Message-ID: <20181101155149.GI2954@hermes.hilbert.loc> (raw )
In-Reply-To: <20181101152723.zq2dtcgntmcmr4br@alvherre.pgsql >
References: <20181101152115.GF2954@hermes.hilbert.loc >
<20181101152723.zq2dtcgntmcmr4br@alvherre.pgsql >
On Thu, Nov 01, 2018 at 12:27:23PM -0300, Alvaro Herrera wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > heap_attisnull (tup=0x0, attnum=5, tupleDesc=0xb2990ef4) at ./build/../src/backend/access/common/heaptuple.c:403
> > 403 ./build/../src/backend/access/common/heaptuple.c: Datei oder Verzeichnis nicht gefunden.
> > (gdb) thread apply all bt full
> >
> > Thread 1 (Thread 0xb4c429c0 (LWP 22367)):
> > #0 heap_attisnull (tup=0x0, attnum=5, tupleDesc=0xb2990ef4) at ./build/../src/backend/access/common/heaptuple.c:403
> > __func__ = "heap_attisnull"
> > #1 0x0087690d in ri_NullCheck (tupDesc=0xb2990ef4, tup=0x0, riinfo=0x2e1d548, rel_is_pk=true) at ./build/../src/backend/utils/adt/ri_triggers.c:2894
> > attnums = 0x2e1d5a4
> > i = 0
> > allnull = true
> > nonenull = true
> > #2 0x00879bf7 in RI_FKey_cascade_del (fcinfo=0xbfbda9e4) at ./build/../src/backend/utils/adt/ri_triggers.c:917
>
> Can you 'print trigdata' in frame 2?
Does this help at all ?
(gdb) frame 2
#2 0x00879bf7 in RI_FKey_cascade_del (fcinfo=0xbfbda9e4) at ./build/../src/backend/utils/adt/ri_triggers.c:917
917 ./build/../src/backend/utils/adt/ri_triggers.c: Datei oder Verzeichnis nicht gefunden.
(gdb) print trigdata
$1 = (TriggerData *) 0xbfbdaca4
It is from another run, however.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
view thread (38+ messages) latest in thread
Message-ID: <20181101155149.GI2954@hermes.hilbert.loc>
Permalink: ../20181101155149.GI2954@hermes.hilbert.loc/
Also on: postgresql.org/message-id/20181101155149.GI2954@hermes.hilbert.loc
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: Karsten.Hilbert@gmx.net, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <20181101155149.GI2954@hermes.hilbert.loc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox