Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
От | Pavel Stehule |
---|---|
Тема | Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan |
Дата | |
Msg-id | CAFj8pRAJdmzzd_8_YiV5yrPy=tpuN9RXqN-3LVtC170B2tQePg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
|
Список | pgsql-hackers |
2017-04-08 2:30 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 4/6/17 14:32, Pavel Stehule wrote:
> I like to see any proposals about syntax or implementation.
>
> Using PRAGMA is one variant - introduced by PLpgSQL origin - Ada
> language. The PRAGMA syntax can be used for PRAGMA autonomous with well
> known syntax. It scales well - it supports function, block or command
> level.
I had pragmas implemented in the original autonomous transactions patch
(https://www.postgresql.org/message-id/659a2fce-b6ee-06de- 05c0-c8ed6a01979e@2ndquadrant. com).
However, the difference there is that the behavior is lexical, specific
to plpgsql, whereas here you are really just selecting run time
behavior. So a GUC, and also something that could apply to other
places, should be considered.
I'll look there - we coordinate work on that.
Regards
Pavel
--
Peter Eisentraut http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: