Re: More guidance on ctid

From: Bernice Southey <bernice(dot)southey(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: More guidance on ctid
Date: 2025-12-23 11:49:37
Message-ID: CAEDh4nz-6HeVGHEU1Pv7Z4y=j44wtkeMyyJ5tfqAT5FHT4sq=w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Bruce Momjian <bruce(at)momjian(dot)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.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2025-12-23 21:32:21 Re: More guidance on ctid
Previous Message Laurenz Albe 2025-12-23 10:19:10 Re: change ON CONFLICT UPDATE