Re: Inconsistent trigger behavior between two temporal leftovers

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Sergei Patiakin <sergei(dot)patiakin(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, "Paul A(dot) Jungwirth" <pj(at)illuminatedcomputing(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Inconsistent trigger behavior between two temporal leftovers
Date: 2026-05-05 21:16:24
Message-ID: CAN4CZFMECdY4eJzd207Z0jn5Hq_AtBHzCrvhFNteRYVN0Ru8tg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

+ /*
+ * Re-copy the original row into leftoverSlot because
+ * ExecInsert may pass leftoverSlot to BEFORE INSERT
+ * triggers, which can modify the slot contents.
+ */

Shouldn't this mention BEFORE ROW INSERT triggers? Everywhere else the
comments/commit message/test is specific about this.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-05-05 21:27:21 Re: PSA: Planning to grease protocol connections during 19beta
Previous Message Ayush Tiwari 2026-05-05 21:01:59 Re: Changing the state of data checksums in a running cluster