From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | mariusz <marius(at)mtvk(dot)pl> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: strange construct with RETURN within plpgsql |
Date: | 2018-02-16 14:43:32 |
Message-ID: | CAFj8pRDDJumWKUYNiyHwAZ4kpdcr2FLrKVmGJO+ZyHzjZ6NPfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2018-02-16 14:20 GMT+01:00 mariusz <marius(at)mtvk(dot)pl>:
> On Fri, 2018-02-16 at 13:51 +0100, Pavel Stehule wrote:
>
>
> > It is not a bug, it is feature. Sometimes not nice. RETURN is keyword
> > in procedural part, but it is nothing in sql part.
> >
> thanks, i haven't thought about such an obvious thing, i feel really
> ashamed.
> of course it makes sense now. i guess what mislead me was that statement
> var := val and forgetting that it's like select into under the hood, and
> even when i put strict select into in examples i didn't spot this (it
> must have been a very long week and i definitely need some rest)
> thanks again
>
Sometimes it is very interesting use #option dump to see "disassambled"
form of plpgsql function.
https://www.slideshare.net/okbob/plpgsql-russiapgconf
Regards
Pavel
>
> regards,
> mj
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Durumdara | 2018-02-16 14:56:58 | Re: Remove default privilege from DB |
Previous Message | Durumdara | 2018-02-16 14:40:42 | Re: Remove default privilege from DB |