Re: Document efficient self-joins / UPDATE LIMIT techniques.
Corey Huinker <corey.huinker@gmail.com>
From: Corey Huinker <corey.huinker@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
pgsql-hackers@lists.postgresql.org
Date: 2024-02-03T20:27:53Z
Lists: pgsql-hackers
Attachments
- v2-0001-Documentation-Show-alternatives-to-LIMIT-on-UPDAT.patch (text/x-patch) patch v2-0001
> > I have changed the status of commitfest entry to "Returned with > Feedback" as Laurenz's comments have not yet been resolved. Please > handle the comments and update the commitfest entry accordingly. > > Here's another attempt, applying Laurenz's feedback: I removed all changes to the SELECT documentation. That might seem strange given that the heavy lifting happens in the SELECT, but I'm working from the assumption that people's greatest need for a ctid self-join will be because they are trying to find the LIMIT keyword on UPDATE/DELETE and coming up empty. Because the join syntax is subtly different between UPDATE and DELETE, I've kept code examples in both, but the detailed explanation is in UPDATE under the anchor "update-limit" and the DELETE example links to it.
Commits
-
Doc: show how to get the equivalent of LIMIT for UPDATE/DELETE.
- 2daeba6a4e49 17.0 landed