| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Bernice Southey <bernice(dot)southey(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: More guidance on ctid |
| Date: | 2025-12-23 21:32:21 |
| Message-ID: | aUsKZRmXgvI-k5Nb@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Dec 23, 2025 at 11:49:37AM +0000, Bernice Southey wrote:
> 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.
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:
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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernice Southey | 2025-12-23 22:27:55 | Re: More guidance on ctid |
| Previous Message | Bernice Southey | 2025-12-23 11:49:37 | Re: More guidance on ctid |