Request a Demo
Home   >   mailing lists

Re: Relax requirement for INTO with SELECT in pl/pgsql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Relax requirement for INTO with SELECT in pl/pgsql
Date
Msg-id 22042.1458623164@sss.pgh.pa.us
Whole thread Raw
In response to Re: Relax requirement for INTO with SELECT in pl/pgsql  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Relax requirement for INTO with SELECT in pl/pgsql
List pgsql-hackers
Tree view 
Pavel Stehule <pavel.stehule@gmail.com> writes:
> I can live with SELECT fx(x). It is little bit dangerous, but this risk can
> be easy detected by plpgsql_check.

Dangerous how?

>> So, I'm -1 on not having any keyword at all.  I have no objection
>> to Merlin's proposal though.  I agree that PERFORM is starting to
>> look a bit silly, since it doesn't play with WITH for instance.

> Isn't time to fix PERFORM instead?

I do not think it can be fixed without embedding knowledge of PERFORM into
the core parser, which I doubt anybody would consider a good idea.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Identifying a message in emit_log_hook.
Next
From: Amit Kapila
Date:
Subject: Re: OOM in libpq and infinite loop with getCopyStart()