Re: An example in UPDATE documentation page is a bit outdated - Mailing list pgsql-docs

From David G. Johnston
Subject Re: An example in UPDATE documentation page is a bit outdated
Date
Msg-id CAKFQuwZH4VqPkTz0bcEK0J_C=25W_G7gA7ZN=bQUddQinnyGKw@mail.gmail.com
Whole thread
In response to An example in UPDATE documentation page is a bit outdated  (PG Doc comments form <noreply@postgresql.org>)
List pgsql-docs
On Sat, Mar 7, 2026 at 1:38 PM PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/18/sql-update.html
Description:

There is an example on UPDATE documentation page --

BEGIN;
-- other operations
SAVEPOINT sp1;
INSERT INTO wines VALUES('Chateau Lafite 2003', '24');
-- Assume the above fails because of a unique key violation,
-- so now we issue these commands:
ROLLBACK TO sp1;
UPDATE wines SET stock = stock + 24 WHERE winename = 'Chateau Lafite 2003';
-- continue with other operations, and eventually
COMMIT;

Now we can use INSERT ... ON CONFLICT DO UPDATE command in this case.


My second reaction was why would we put either variant on the update command reference page.

Admittedly both of those examples are probably good to have somewhere, and I'm not sure where would be the most discoverable place.

I'd rather remove the example and write a paragraph pointing the reader to the savepoint and insert pages if they have a need to perform a conditional insert/update pairing.

David J.

pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: An example in UPDATE documentation page is a bit outdated
Next
From: PG Doc comments form
Date:
Subject: INTERVAL output format for iso_8601 is without dashes