On Tue, Dec 23, 2025 at 10:27:55PM +0000, Bernice Southey wrote: > Bruce Momjian <[email protected]> wrote: > > 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 meant about all the other stuff (order by and limit etc). At one > point the patch had more duplication across update and delete. > > > 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. > Yes. > I only queried adding it to both because I remembered the original > thread. I agree the visibility of the duplicate warning is better. > > [From the thread] > > > It is similar, but the idea here is to aid in discovery. A user might > > > miss the > > > technique for update if it's only documented in delete, and even if they > > > did see > > > it there, they might not realize that it works for both UPDATE and DELETE. > > > We could make reference links from one to the other, but that seems like > > > extra > > > work for the reader. > > I don't agree with bloating the documentation with redundant examples just > > to save a user a click. I like the idea of a link
Okay, let's give it another 12 hours and I will apply it tomorrow, thanks. -- Bruce Momjian <[email protected]> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
