On Tue, Dec 23, 2025 at 11:49:37AM +0000, Bernice Southey wrote:
> Bruce Momjian <[email protected]> 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.
Great.
> There was a strong preference for not duplicating the explanatory text
> when the examples were added. Perhaps delete doesn't need the new
> line?
Uh, where did you see that? I found the original thread and I don't see
any mention of a warning, or not wanting a warning:
https://www.postgresql.org/message-id/flat/CADkLM%3DcaNEQsUwPWnfi2jR4ix99E0EJM_3jtcE-YjnEQC7Rssw%40mail.gmail.com
I feel we need a warning specifically because people will find this
query, particularly in the very visible UPDATE/DELETE man pages, and not
realize ctid only has a few save use-cases.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
