From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Improve comment on why we need ctid->(cmin,cmax) mapping.
Date: Fri, 30 Jun 2023 15:32:20 +0000
Message-ID: <E1qFG6e-001DUT-9r@gemulon.postgresql.org> (raw)
Improve comment on why we need ctid->(cmin,cmax) mapping.
Combocids are only part of the problem. Explain the problem in more detail.
Reviewed-by: Andres Freund
Discussion: https://www.postgresql.org/message-id/1ba2899e-77f8-7866-79e5-f3b7d1251a3e@iki.fi
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a0dd4c95b9dfb9ed679ff8aa6a3beab98969034f
Modified Files
--------------
src/backend/replication/logical/snapbuild.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: heikki.linnakangas@iki.fi, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Improve comment on why we need ctid->(cmin,cmax) mapping.
In-Reply-To: <E1qFG6e-001DUT-9r@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox