On Thu, Dec 4, 2025, at 5:58 PM, Hannu Krosing wrote:
> Please find attached a patch that makes tuple ids and info about
> weather it was plain or HOT update available to logical decoding
> callbacks.
>
My first impression was: why do you want to expose an internal information that
is mostly useless for a broader audience? The logical decoding infrastructure
is a general purpose solution for streaming modifications made to Postgres.
Could you elaborate how other consumers (DBMS, data store, ...) would use it?
> My planned use case is for reliable logical replication of tables
> without primary key or other declared IDENTITY (as long as there are
> no updates on target, or at leas no non-hot updates)
>
Wait, we already have a mechanism to handle it: replica identity. What is the
advantage of this proposal in comparison with replica identity?
It seems a Postgres-centric solution that you didn't provide strong arguments
in favor of it. How would logical replication take advantage of such change? If
that's the case, share the pgoutput and logical replication changes.
--
Euler Taveira
EDB https://www.enterprisedb.com/
