| From: | Mor Lehr <mor(dot)lehr(at)deel(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error |
| Date: | 2024-06-02 15:42:38 |
| Message-ID: | CALyvM2ZcywTKdxgYZhAXjmdxTuBT2RyW+cn0XwwHxXbfvXMBEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sunday, June 2, 2024, Mor Lehr <mor(dot)lehr(at)deel(dot)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.
>>
>
>
> https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-ASSIGNMENT
>
> “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.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Floris Van Nee | 2024-06-02 21:31:56 | RE: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure |
| Previous Message | David G. Johnston | 2024-06-02 15:31:42 | Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error |