public inbox for pgsql-docs@postgresql.org  

help / color / mirror / Atom feed

From: Bernice Southey <bernice.southey@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: More guidance on ctid
Date: Tue, 23 Dec 2025 11:49:37 +0000
Message-ID: <CAEDh4nz-6HeVGHEU1Pv7Z4y=j44wtkeMyyJ5tfqAT5FHT4sq=w@mail.gmail.com> (raw)
In-Reply-To: <aUnBfsbUbObEcY42@momjian.us>
References: <CAEDh4nyn5swFYuSfcnGAbpQrKOc47Hh_ZyKVSPYJcu2P=51Luw@mail.gmail.com>
	<aSTL3rgmztLq1UIH@momjian.us>
	<CAEDh4nzDMoRDZMDGGxKHzJ5hZscmvT2FWioTzQ6A0aJVtCO8NQ@mail.gmail.com>
	<aUnBfsbUbObEcY42@momjian.us>

Bruce Momjian <bruce@momjian.us> wrote:
> What I did do was to explain why ctid was safe in this
> use-case.  I also strengthened the documentation that ctid is not valid
> for row references.
I like this, explaining the risk is much better. I couldn't think of a
simple way to do it.

There was a strong preference for not duplicating the explanatory text
when the examples were added. Perhaps delete doesn't need the new
line?

Thanks, Bernice

PS - Thanks for your postgres internals videos. I found them a few
months ago and they lit up my brain.

reply

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-docs@postgresql.org
  Cc: bernice.southey@gmail.com, bruce@momjian.us, pgsql-docs@lists.postgresql.org
  Subject: Re: More guidance on ctid
  In-Reply-To: <CAEDh4nz-6HeVGHEU1Pv7Z4y=j44wtkeMyyJ5tfqAT5FHT4sq=w@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox