Re: proposal: plpgsql, new check for extra_errors - strict_expr_check

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
Date: 2024-06-16 14:42:51
Message-ID: CAB-JLwZtUdr7ASJVa6Tvg5gYJWL+=tnQvf8X3sX=Szeigti5KA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em dom., 16 de jun. de 2024 às 11:37, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
escreveu:

>
> What is the expected benefit? Generally PL/pgSQL has very strict syntax -
> and using double semicolons makes no sense.
>
> exactly, makes no sense. That is because it should be ignored, right ?
But ok, if this is a different issue, that´s fine.

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-06-16 14:58:33 Re: Using LibPq in TAP tests via FFI
Previous Message Pavel Stehule 2024-06-16 14:36:33 Re: proposal: plpgsql, new check for extra_errors - strict_expr_check