pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Butz <tbutz@optitool.de>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16095: Segfault while executing trigger
Date: Wed, 6 Nov 2019 12:48:16 +0100 (CET)
Message-ID: <1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de> (raw)

> Thomas, can you try with that patch and see if it fixes the problem 
> for you? We're quite close to 12.1 release, so if there's more to fix, 
> it'd be better to find out ASAP. 
> 
> Note that this theory requires that the query we see being executed within 
> a BEFORE UPDATE trigger had itself fired a BEFORE UPDATE trigger, and that 
> there'd been concurrent commits causing EPQ to run. That doesn't seem 
> exactly implausible, but it's data not evident in your report. 

That seems to be the case because the software is running parallel UPDATE requests against a table called "placex" which has an active trigger[1]: 


CREATE TRIGGER placex_before_update BEFORE UPDATE ON placex 
FOR EACH ROW EXECUTE PROCEDURE placex_update(); 


and the placex_update() function is again issuing UPDATE statements[2]: 


UPDATE placex set linked_place_id = null, indexed_status = 2 
where linked_place_id = NEW.place_id; 


[1] https://github.com/openstreetmap/Nominatim/blob/65daef70c1f9aa80e6d37fc12198309e49b883ca/sql/tables.... 
[2] https://github.com/openstreetmap/Nominatim/blob/05d7f9139247981cc7d9edc1edca9492e94b516b/sql/functio... 


Are there any prebuilt deb packages with this patch? 



Kind regards 

Thomas Butz 

view thread (8+ messages)  latest in thread

Message-ID: <1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de>
Permalink:  ../1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de/
Also on:    postgresql.org/message-id/1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tbutz@optitool.de
  Subject: Re: BUG #16095: Segfault while executing trigger
  In-Reply-To: <1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de>
  References: <1820932263.377949.1573040896379.JavaMail.zimbra@optitool.de>

* 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