Re: Dead code in logical decoding of speculative insertions

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, akapila(at)postgresql(dot)org
Subject: Re: Dead code in logical decoding of speculative insertions
Date: 2026-03-06 09:38:09
Message-ID: CAA4eK1KSQyinK+UWH9Sdm+foTcJuA9de=+Gac0BcG-RLZbot1g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 5, 2026 at 2:59 PM Antonin Houska <ah(at)cybertec(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-03-06 09:38:30 Re: Emitting JSON to file using COPY TO
Previous Message Ashutosh Bapat 2026-03-06 09:32:32 Re: SQL Property Graph Queries (SQL/PGQ)