Re: Undocumented optionality of handler_statements

2024-10-16 Thread David G. Johnston
On Wednesday, October 16, 2024, Bruce Momjian wrote: > On Wed, Sep 11, 2024 at 03:37:17PM +0900, Michael Paquier wrote: > > On Tue, Jul 23, 2024 at 01:25:39PM +0200, Philipp Salvisberg wrote: > > > read "optional" as "mandatory". > > > > They're optional, like in empty being optional. If not spe

Re: Undocumented optionality of handler_statements

2024-10-16 Thread Bruce Momjian
On Wed, Sep 11, 2024 at 03:37:17PM +0900, Michael Paquier wrote: > On Tue, Jul 23, 2024 at 01:25:39PM +0200, Philipp Salvisberg wrote: > > read "optional" as "mandatory". > > They're optional, like in empty being optional. If not specified, the > block goes to its END. > > > Therefore, I suggest

Re: Undocumented optionality of handler_statements

2024-09-13 Thread David G. Johnston
On Friday, September 13, 2024, Philipp Salvisberg < philipp.salvisb...@gmail.com> wrote: > >> Therefore, I suggest to change this example by adding a NULL > >> statement as in other examples. This change would make the > >> documentation consistent and handle the optionality of > >> handler_statem

Re: Undocumented optionality of handler_statements

2024-09-13 Thread Philipp Salvisberg
>> Therefore, I suggest to change this example by adding a NULL >> statement as in other examples. This change would make the >> documentation consistent and handle the optionality of >> handler_statements as an implementation detail. I created a patch >> for plpgsql.sgml based on the master branch

Re: Undocumented optionality of handler_statements

2024-09-10 Thread Michael Paquier
On Tue, Jul 23, 2024 at 01:25:39PM +0200, Philipp Salvisberg wrote: > read "optional" as "mandatory". They're optional, like in empty being optional. If not specified, the block goes to its END. > Therefore, I suggest to change this example by adding a NULL > statement as in other examples. This

Re: Undocumented optionality of handler_statements

2024-07-23 Thread Philipp Salvisberg
On 23 Jul 2024, at 01:39, Michael Paquier wrote:On Mon, Jul 22, 2024 at 01:55:52PM +, PG Doc comments form wrote:Inhttps://www.postgresql.org/docs/16/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPINGhandler_statements are documented as optional.However, the following example shows that ha

Re: Undocumented optionality of handler_statements

2024-07-22 Thread Michael Paquier
On Mon, Jul 22, 2024 at 01:55:52PM +, PG Doc comments form wrote: > 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.

Undocumented optionality of handler_statements

2024-07-22 Thread PG Doc comments form
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. Ho