Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan |
Дата | |
Msg-id | 746a1f27-8a8c-b67f-ca4f-ec2e94426349@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
|
Список | pgsql-hackers |
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 thereis 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. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: