Re: [BUG] Query with postgres fwd deletes more tuples than it should - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: [BUG] Query with postgres fwd deletes more tuples than it should
Date
Msg-id CAPmGK17A+ZYin1iBZ5rERWu8VHKbkpCHyBSzk1AW8TAfFS9q_A@mail.gmail.com
Whole thread Raw
In response to Re: [BUG] Query with postgres fwd deletes more tuples than it should  (Daniil Davydov <3danissimo@gmail.com>)
List pgsql-hackers
On Wed, Sep 17, 2025 at 10:11 PM Daniil Davydov <3danissimo@gmail.com> wrote:
> On Wed, Sep 17, 2025 at 6:46 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> > On Wed, Sep 17, 2025 at 2:46 PM <jiaoshuntian@highgo.com> wrote:
> > > I think a good way to fix would be to use `(tableoid, ctid)` together as the row
> > > identifier in row-by-row updates/deletes. This combination is unique
> > > across partitions and avoids the incorrect behavior, while still keeping
> > > LIMIT support.
> >
> > Agreed; actually I created such a fix as well a long time ago, but
> > unfortunately it has many issues...
>
> I'll try to help with implementation of the proposed idea.

Great!

> BTW, maybe we should move commitfest entry [1] to the next CF?
>
> [1] https://commitfest.postgresql.org/patch/1819/

My plan is to re-add this to CF when I address Tom's comments [2], but
I don't yet have a clear solution for that.  BUT: if you want to work
on it, feel free.

Best regards,
Etsuro Fujita

[2] https://www.postgresql.org/message-id/1590.1542393315%40sss.pgh.pa.us



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [Patch] add new parameter to pg_replication_origin_session_setup
Next
From: Dilip Kumar
Date:
Subject: Re: Incorrect logic in XLogNeedsFlush()