Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Fetter" <dfetter(at)vmware(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails
Date: 2011-06-18 20:30:51
Message-ID: 24370.1308429051@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David Fetter" <dfetter(at)vmware(dot)com> writes:
> IF EXISTS (SELECT 1 INTO STRICT i) THEN
> RAISE NOTICE '%', a;
> END IF;

Umm ... are you just complaining that the error message isn't very
helpful, or are you actually expecting that to do something useful?
If the latter, what exactly? I'm particularly confused by your use
of the STRICT option here, because if we did support that, I would
expect the STRICT to throw an error if there were not exactly one
matching row, making the EXISTS test 100% pointless.

But the short answer is that we don't support INTO in sub-selects,
and in general I doubt that we ever will, since in most cases the
behavior wouldn't be very well-defined. It might be worth a TODO
to provide a better error message than "syntax error", though.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2011-06-18 22:32:24 BUG #6068: automatic analyze runs endlessly
Previous Message Pavel Stehule 2011-06-18 20:18:42 Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails