Dead code in logical decoding of speculative insertions

Started by Antonin Houskaabout 2 months ago3 messageshackers
Jump to latest
#1Antonin Houska
ah@cybertec.at

Since commit 4daa140a2f50 adds the INTERNAL_SPEC_ABORT change, I think it's no
longer necessary to care about "pending speculations" at the time we receive
the next INTERNAL_SPEC_INSERT change.

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

Attachments:

0001-Remove-cleanup-of-speculative-insert.patchtext/x-diffDownload+2-7
#2Amit Kapila
amit.kapila16@gmail.com
In reply to: Antonin Houska (#1)
Re: Dead code in logical decoding of speculative insertions

On Thu, Mar 5, 2026 at 2:59 PM Antonin Houska <ah@cybertec.at> wrote:

Since commit 4daa140a2f50 adds the INTERNAL_SPEC_ABORT change, I think it's no
longer necessary to care about "pending speculations" at the time we receive
the next INTERNAL_SPEC_INSERT change.

Right, I also think so. Did you find it via code review or some other way?

--
With Regards,
Amit Kapila.

#3Antonin Houska
ah@cybertec.at
In reply to: Amit Kapila (#2)
Re: Dead code in logical decoding of speculative insertions

Amit Kapila <amit.kapila16@gmail.com> wrote:

On Thu, Mar 5, 2026 at 2:59 PM Antonin Houska <ah@cybertec.at> wrote:

Since commit 4daa140a2f50 adds the INTERNAL_SPEC_ABORT change, I think it's no
longer necessary to care about "pending speculations" at the time we receive
the next INTERNAL_SPEC_INSERT change.

Right, I also think so. Did you find it via code review or some other way?

Yes, I noticed that via code review, while investigating a crash:

[1]: /messages/by-id/CAFC+b6o2yzA80YmfEhmMO9puN8qvGRvr-15BBLn3UmJxPfpr2w@mail.gmail.com

--
Antonin Houska
Web: https://www.cybertec-postgresql.com