|From:||Thomas Butz <tbutz(at)optitool(dot)de>|
|Subject:||Re: BUG #16095: Segfault while executing trigger|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> 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:
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:
UPDATE placex set linked_place_id = null, indexed_status = 2
where linked_place_id = NEW.place_id;
Are there any prebuilt deb packages with this patch?
|Next Message||vignesh C||2019-11-06 11:50:02||Reorderbuffer crash during recovery|
|Previous Message||Fabien COELHO||2019-11-06 11:31:02||Re: BUG #16096: psql (non-interactive mode) SQL multi-request commands don't report all feedback ?!|