Re: Inconsistent trigger behavior between two temporal leftovers
Paul A Jungwirth <pj@illuminatedcomputing.com>
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
To: Sergei Patiakin <sergei.patiakin@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut <peter@eisentraut.org>
Date: 2026-04-22T18:37:22Z
Lists: pgsql-hackers
On Tue, Apr 14, 2026 at 10:28 PM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
> I wrote a fix before I saw yours, but they are nearly the same. I
> tried to share more code between the first & subsequent passes, but
> it's hard to do with the mapping case. So the fix you have here looks
> great to me.
I made a commitfest entry for this:
https://commitfest.postgresql.org/patch/6702/
I am currently listed as both an author and reviewer. Sergei, I'd like
to add you as the author, but I don't see an account with your name in
the commitfest app. If you have one, please feel free to add yourself
(or let me know which account I should use).
Yours,
--
Paul ~{:-)
pj@illuminatedcomputing.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix cross-leftover pollution in FOR PORTION OF insert triggers
- 993a7aa0e4af 19 (unreleased) landed