Re: Inconsistent trigger behavior between two temporal leftovers
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Sergei Patiakin <sergei.patiakin@enterprisedb.com>,
pgsql-hackers@lists.postgresql.org
Cc: "Paul A. Jungwirth" <pj@illuminatedcomputing.com>
Date: 2026-04-27T09:40:15Z
Lists: pgsql-hackers
On 08.04.26 14:50, Sergei Patiakin wrote: > Attaching a patch that makes the behavior more consistent. Maybe this is not a problem in your patch, but I'm confused under what circumstances one is supposed to use the return value of execute_attr_map_slot(). Existing code appears to be inconsistent about that, but there isn't any explanation anywhere I can see.
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