Re: [HACKERS] proposal: session server side variables (fwd)
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] proposal: session server side variables (fwd) |
Дата | |
Msg-id | 20170107234655.GA13329@momjian.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] proposal: session server side variables (fwd) (Fabien COELHO <coelho@cri.ensmp.fr>) |
Список | pgsql-hackers |
On Thu, Jan 5, 2017 at 11:45:24AM +0100, Fabien COELHO wrote: > > <Argh, wrong sender again, sorry [again] for the repost. > I must tweak my mail client configuration...> > > >>>Good. So we seem to agree that GUCS are transactional? > > > >I'm surprised, I never knew this. > > I must admit that it was also a (good) surprise for me. > > The documentation says it: > > """ > If SET (or equivalently SET SESSION) is issued within a transaction that is > later aborted, the effects of the SET command disappear when the transaction > is rolled back. Once the surrounding transaction is committed, the effects > will persist until the end of the session, unless overridden by another SET. > """ > > But I have not found anything clear about user-defined parameters. Uh, I think it is a missing feature, i.e.: https://wiki.postgresql.org/wiki/Todo#AdministrationHave custom variables be transaction-safe https://www.postgresql.org/message-id/4B577E9F.8000505@dunslane.net -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
В списке pgsql-hackers по дате отправления: