Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vYBig-00FVBt-1z for pgsql-docs@arkaria.postgresql.org; Tue, 23 Dec 2025 23:23:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vYBif-002Zwb-1v for pgsql-docs@arkaria.postgresql.org; Tue, 23 Dec 2025 23:23:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vYBif-002ZwP-18 for pgsql-docs@lists.postgresql.org; Tue, 23 Dec 2025 23:23:10 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vYBie-002G7b-1y for pgsql-docs@lists.postgresql.org; Tue, 23 Dec 2025 23:23:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=rY1GU/iVQFk4Fx0+V+H5KDgZ9vYgSbHhPxr8+8BXrq8=; b=sHogP Dn5GIR2FsveFIRr1LWYm9wRUWjGuuAHpT4vZM2V1HUzRFNDZYdYn/C8RpV3lyy+RX6GF9TYHnPmcq Xpus2tf5HztaAE81unajaR9lvVryzX9L8+WrJEJI7zh6OV4Q6GO+FPuBkXGL4Ef/zgw5XO8LH1/n9 bZhPzZiZeFCZgtOOOXgoMFeF5T3SfI14HAzSP6xO0hJ4h2I5ekhxKpCDdm2vjnahlZBqYryUgebz3 qH+/zc6eUpgy8s6eZUvHvHgbHT+wTJBDsyOejhMnsMGISqL2boZSPhPwfjU6MWNe4cMqmSyb29fH1 zRYXu7iHfGEFRocT6skResm5XuHGA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vYBid-00000002hNf-1Ms3; Tue, 23 Dec 2025 18:23:07 -0500 Date: Tue, 23 Dec 2025 18:23:07 -0500 From: Bruce Momjian To: Bernice Southey Cc: pgsql-docs@lists.postgresql.org Subject: Re: More guidance on ctid Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Dec 23, 2025 at 10:27:55PM +0000, Bernice Southey wrote: > Bruce Momjian 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.