| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Subject: | Re: PoC plpgsql - possibility to force custom or generic plan |
| Date: | 2017-09-09 05:34:48 |
| Message-ID: | CAFj8pRBMWFbsJbbLwD0RjGePmjm4xTtUvAmLCZk9V=+_+2rW2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >
> > SET x = .., y = .. SELECT ... ;
>
> This seems pretty ugly from a syntax perspective.
>
> We already have 'SET LOCAL', which manages scope to the current
> transaction. How about SET BLOCK which would set until you've left
> the current statement block?
>
This is reason why PRAGMA was designed - it can works on function, block,
or statement level. But only in block based PL languages.
>
> merlin
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-09-09 06:12:33 | Re: Re: proposal - using names as primary names of plpgsql function parameters instead $ based names |
| Previous Message | Tom Lane | 2017-09-09 04:43:45 | Re: Still another race condition in recovery TAP tests |