| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | bashtanov(at)imap(dot)cc |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql pragma statement |
| Date: | 2018-12-05 14:05:20 |
| Message-ID: | CAFj8pRAzaL+Uh9i5_GR+YEHcnmNyvKvuo4OnoM-Stj2pxV5Q9w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
st 5. 12. 2018 v 14:42 odesílatel Alexey Bashtanov <bashtanov(at)imap(dot)cc>
napsal:
>
>
>> You can use PERFORM as a workaround:
>>
>> PERFORM 'PRAGMA', 'cmdtype', 'CREATE';
>>
>> There's some overhead when executing, but probably not too much.
>>
>
> Thank you for tip, but I have not any idea, how it can work?
>
>
> Well, I thought you were for a comment-like thing that remains there when
> compiled and can act as a hint for your static analysis extension.
> Surely this PERFORM won't impose any hints on the following statement
> itself.
> But maybe your extension could read the PERFORM statement preceding it and
> treat it as an annotation hint for the following statement.
>
PERFORM is +/- SELECT, so if I use PERFORM, I have to modify this statement.
> Best,
> Alex
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-12-05 14:09:00 | Re: proposal: plpgsql pragma statement |
| Previous Message | Pavel Luzanov | 2018-12-05 14:03:17 | Re: proposal: plpgsql pragma statement |