pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: philipp.salvisberg@gmail.com
Subject: Undocumented optionality of handler_statements
Date: Mon, 22 Jul 2024 13:55:52 +0000
Message-ID: <172165655256.710.2097726158572647813@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/plpgsql-control-structures.html
Description:
In
https://www.postgresql.org/docs/16/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING
handler_statements are documented as optional.
However, the following example shows that handler_statements can be omitted.
drop table if exists t;
create table t (id integer not null primary key);
do $$
begin
insert into t (id) values (1), (1);
exception when unique_violation then
-- ignore without calling null statement
end
$$;
I stumbled over it when running the example documented in
https://www.postgresql.org/docs/current/plpgsql-trigger.html#PLPGSQL-TRIGGER-SUMMARY-EXAMPLE
- it also contains an exception handler without handler statements.
view thread (9+ messages) latest in thread
Message-ID: <172165655256.710.2097726158572647813@wrigleys.postgresql.org>
Permalink: ../172165655256.710.2097726158572647813@wrigleys.postgresql.org/
Also on: postgresql.org/message-id/172165655256.710.2097726158572647813@wrigleys.postgresql.org
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: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, philipp.salvisberg@gmail.com
Subject: Re: Undocumented optionality of handler_statements
In-Reply-To: <172165655256.710.2097726158572647813@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox