public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Bernice Southey <[email protected]>
Cc: [email protected]
Subject: Re: More guidance on ctid
Date: Wed, 24 Dec 2025 14:47:01 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEDh4nyBQe8rc_OGwZW-pevAXc8r2sHW6EbYzCq40ZrudxJOng@mail.gmail.com>
References: <[email protected]>
<CAEDh4nzDMoRDZMDGGxKHzJ5hZscmvT2FWioTzQ6A0aJVtCO8NQ@mail.gmail.com>
<[email protected]>
<CAEDh4nz-6HeVGHEU1Pv7Z4y=j44wtkeMyyJ5tfqAT5FHT4sq=w@mail.gmail.com>
<[email protected]>
<CAEDh4nwv22R3WBC-JW96YWfrvgA9UN=rDx11T4+zNrGVpXg5BQ@mail.gmail.com>
<[email protected]>
<CAEDh4nyStja3R4X6qW_zpKz2w8EPUTsHQ8S0k9_saPA7BT+quw@mail.gmail.com>
<[email protected]>
<CAEDh4nyBQe8rc_OGwZW-pevAXc8r2sHW6EbYzCq40ZrudxJOng@mail.gmail.com>
On Wed, Dec 24, 2025 at 07:38:07PM +0000, Bernice Southey wrote:
> Bruce Momjian <[email protected]> wrote:
> > We could go in the direction you suggested, but it seems out-of-place in
> > the UPDATE/DELETE docs since it gets into a lot of details. Maybe in
> > the locking chapter?
> How about if the UPDATE and DELETE examples only show how to get limit
> and order by with a cte, and remove all references to locking. No for
> update, deadlocks etc. The examples use primary keys and not ctid.
> Anyone just trying to do simple limit and order by without locking
> problems will get what they need, and won't be confused by the locking
> complexity. Anyone trying to solve lock contention needs to understand
> locking and should be looking at that chapter. The explanation for
> deadlock avoidance should be there as you suggest. Perhaps the update
> and delete examples can link to them. If you think this is the right
> approach I'm willing to give it a go?
I am not the author of the original ctid doc patch, but I believe the
goal was to use ctid so we don't need to use needless index lookups for
primary keys.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: More guidance on ctid
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox