| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: proposal: session server side variables |
| Date: | 2017-01-05 00:35:11 |
| Message-ID: | CAMsr+YGigrp9H3ari_Q55c4XAVRVYv7orkP+XQLNEhdWaRHRxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 January 2017 at 01:49, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
>> ok understand
>
>
> Good. So we seem to agree that GUCS are transactional?
No. We don't agree. They aren't.
The effects of SET LOCAL are reverted whether you commit or rollback.
The effects of SET SESSION are never reverted, whether you commit or roll back.
craig=> SET x.s = 'x';
SET
craig=> BEGIN;
BEGIN
craig=> SET LOCAL x.s = 'y';
SET
craig=> COMMIT;
COMMIT
craig=> SHOW x.s;
x.s
-----
x
(1 row)
There are simply different scopes, one of which is the transaction scope.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-01-05 00:36:32 | Re: proposal: session server side variables |
| Previous Message | Vitaly Burovoy | 2017-01-05 00:34:15 | Re: identity columns |