Re: Inconsistent trigger behavior between two temporal leftovers - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Inconsistent trigger behavior between two temporal leftovers
Date
Msg-id 6f0b82b0-4084-4bc8-95b2-237945d35e0a@eisentraut.org
Whole thread
In response to Re: Inconsistent trigger behavior between two temporal leftovers  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
List pgsql-hackers
On 05.05.26 23:48, Paul A Jungwirth wrote:
> On Tue, May 5, 2026 at 2:16 PM Zsolt Parragi <zsolt.parragi@percona.com> wrote:
>>
>> + /*
>> + * 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.
> 
> I agree being specific is helpful. Here is an updated patch.

committed




pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: jian he
Date:
Subject: Re: Row pattern recognition