Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error - Mailing list pgsql-bugs

From Mor Lehr
Subject Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Date
Msg-id CALyvM2ZcywTKdxgYZhAXjmdxTuBT2RyW+cn0XwwHxXbfvXMBEA@mail.gmail.com
Whole thread Raw
In response to Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
Thanks for the reference.
We learn new stuff every day.

You can close the case.
Thanks, Mor


On Sun, Jun 2, 2024, 18:31 David G. Johnston <david.g.johnston@gmail.com> wrote:
On Sunday, June 2, 2024, Mor Lehr <mor.lehr@deel.com> wrote:
Thanks for the prompt reply.
Can you please refer me to the section in the documentation that describes this behavior?
This (automatically interperting 1 as select 1) is totally an unexpected behavior for me.


“As explained previously, the expression in such a statement is evaluated by means of an SQL SELECT command sent to the main database engine.”

David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Next
From: Floris Van Nee
Date:
Subject: RE: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure