pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Thu, 1 Nov 2018 17:00:07 +0100
Message-ID: <20181101160007.GJ2954@hermes.hilbert.loc> (raw)
In-Reply-To: <18072.1541087036@sss.pgh.pa.us>
References: <20181101152723.zq2dtcgntmcmr4br@alvherre.pgsql>
	<18072.1541087036@sss.pgh.pa.us>

On Thu, Nov 01, 2018 at 11:43:56AM -0400, Tom Lane wrote:

> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > Ah, now this is interesting.  Can you please supply the definition of
> > the table?  I'm wondering if there is a partitioned table with an FK to
> > this one.  I'm not quite seeing how come 'tup' is NULL there.
> 
> Yeah, apparently we've passed a null OLD tuple to an RI_FKey_cascade_del
> trigger, which surely shouldn't happen.  It'd be interesting to look at
> the set of triggers on this table.  I don't entirely trust psql's \d
> to show us reality if there's something screwed up about the triggers,
> so in addition to \d output, could we see
> 
> select * from pg_trigger where tgrelid  = 'ref.auto_hint'::regclass;

Ausgabeformat ist »wrapped«.
 tgrelid |            tgname             | tgfoid | tgtype | tgenabled | tgisinternal | tgconstrrelid | tgconstrindid | tgconstraint | tgdeferrable | tginitdeferred | tgnargs | tgattr | tgargs | tgqual | tgoldtable | tgnewtable 
---------+-------------------------------+--------+--------+-----------+--------------+---------------+---------------+--------------+--------------+----------------+---------+--------+--------+--------+------------+------------
  111088 | RI_ConstraintTrigger_a_116970 |   1646 |      9 | O         | t            |        116789 |        111099 |       116969 | f            | f              |       0 |        | \x     |        |            | 
  111088 | RI_ConstraintTrigger_a_116971 |   1649 |     17 | O         | t            |        116789 |        111099 |       116969 | f            | f              |       0 |        | \x     |        |            | 
  111088 | zt_ins_auto_hint              | 141652 |      7 | O         | f            |             0 |             0 |            0 | f            | f              |       0 |        | \x     |        |            | 
  111088 | zt_upd_auto_hint              | 141654 |     19 | O         | f            |             0 |             0 |            0 | f            | f              |       0 |        | \x     |        |            | 
  111088 | zt_del_auto_hint              | 141656 |     11 | O         | f            |             0 |             0 |            0 | f            | f              |       0 |        | \x     |        |            | 
(5 Zeilen)


BTW, do you want me to attach text files or include into the
body (potential wrapping issues on display) ?

Thanks,
Karsten
-- 
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B




view thread (38+ messages)  latest in thread

Message-ID: <20181101160007.GJ2954@hermes.hilbert.loc>
Permalink:  ../20181101160007.GJ2954@hermes.hilbert.loc/
Also on:    postgresql.org/message-id/20181101160007.GJ2954@hermes.hilbert.loc

 · 

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, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, pgsql-general@lists.postgresql.org
  Subject: Re: backend crash on DELETE, reproducible locally
  In-Reply-To: <20181101160007.GJ2954@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