Postgres Pro
Downloads
Home   >   mailing lists

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-JLwbDoN7BZwYjNgP3gq-AC=3w9s7QCyR-kWg51NqG4pfqJA@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
Tree view
Em dom., 16 de jun. de 2024 às 12:11, Pavel Stehule <pavel.stehule@gmail.com> escreveu:
I don't follow this idea - when it does not make sense, then why do you use it?  It can be a signal of some issue in your code.

I don't use it, but sometimes it occurs, and there are lots of languages which ignore it, so it would be cool if plpgsql does it too.
 
If you do this, works
set search_path to public;;;

but if you do the same inside a block, it does not.

regards
Marcos

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Removing unneeded self joins
Next
From: Heikki Linnakangas
Date:
Subject: Re: Bugfix and improvements in multixact.c