Re: Add TG_* vars for FOR PORTION OF

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Add TG_* vars for FOR PORTION OF
Date: 2026-09-17 02:44:13
Message-ID: CA+renyV2NRb-XZj0+wpSsHcDYQwHhQXNRp0cOGuDvO4kKJDcTg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 6, 2026 at 6:10 AM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> Hello!
>
> I have a generic design question: as I mentioned in [1], we also have
> a similar situation outside FOR PORTION OF when a plain update moves a
> record across partitions. Maybe we should have a detection logic that
> can answer this question in a generic way, that could be also used by
> every similar code in the future? Giving users simply the ability to
> ask "Was this before insert trigger caused by an implicit insert?",
> for example.

Thank you for the review! Since FPO was reverted from v19, I will fold
your feedback into a new submission for v20. I'm going to mark the
commitfest entry for this with as Withdrawn.

Yours,

--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-09-17 02:44:44 Re: Optimize truncation logic to reduce AccessExclusive lock impact
Previous Message Richard Guo 2026-09-17 02:40:57 Re: remove_useless_joins vs. bug #19560