>> 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
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
> On 22 Jul 2024, at 18:24, Tom Lane wrote:
>
> PG Doc comments form writes:
>> The following documentation comment has been logged on the website:
>> Page: https://www.postgresql.org/docs/16/plpgsql-cursors.html
>> Description:
>
>> The documentation shows this example for the MOVE statement
> On 22 Jul 2024, at 15:18, jian he wrote:
>
> On Mon, Jul 22, 2024 at 8:38 PM PG Doc comments form
> wrote:
>>
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/16/plpgsql-errors-and-messages.html
>> Description:
>>
>> The us
