Re: proposal: plpgsql, new check for extra_errors - strict_expr_check - Mailing list pgsql-hackers

From Marcos Pegoraro
Subject Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
Date
Msg-id CAB-JLwZtUdr7ASJVa6Tvg5gYJWL+=tnQvf8X3sX=Szeigti5KA@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql, new check for extra_errors - strict_expr_check  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
List pgsql-hackers
Em dom., 16 de jun. de 2024 às 11:37, Pavel Stehule <pavel.stehule@gmail.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

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: plpgsql, new check for extra_errors - strict_expr_check
Next
From: Andrew Dunstan
Date:
Subject: Re: Using LibPq in TAP tests via FFI