pgsql: Improve comment on why we need ctid->(cmin,cmax) mapping.

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Improve comment on why we need ctid->(cmin,cmax) mapping.
Date: 2023-06-30 15:32:20
Message-ID: E1qFG6e-001DUT-9r@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2023-06-30 18:35:46 Re: pgsql: Fix search_path to a safe value during maintenance operations.
Previous Message Bruce Momjian 2023-06-30 12:37:39 pgsql: doc: PG _14_ relnotes, remove duplicate commit comment