From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL PERFORM with CTE |
Date: | 2013-08-20 13:46:54 |
Message-ID: | CAFj8pRCBGCA8jc7AigF7W4=4Sm2MR28PFXPtmOTCZeDmhRedvA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/8/20 David E. Wheeler <david(at)justatheory(dot)com>
> On Aug 20, 2013, at 3:38 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
> > pg_notify returns void, so there are no necessary casting to void
> >
> > so enhanced check - so all returned columns are void should be enough
>
> What if I call another function I wrote myself that returns an INT, but I
> do not care about the INT? Maybe that function does the insert and returns
> the number of inserted rows.
>
> I can think of all kinds of reasons this might be the case; whether they
> are good or bad approaches is immaterial: sometimes you work with what you
> have.
>
> I am find with PERFORM to determine when a query's results should be
> discarded. I just think it needs to cover a few more cases.
>
yes
I understand. I'll look, how PERFORM can be fixed
Regards
Pavel
>
> Best,
>
> David
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-08-20 14:09:51 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Previous Message | David E. Wheeler | 2013-08-20 13:43:21 | Re: PL/pgSQL PERFORM with CTE |