From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, 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> |
Subject: | Re: proposal: session server side variables |
Date: | 2017-01-05 00:42:59 |
Message-ID: | ce617ce2-ede4-0737-8368-75c16a833297@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/04/2017 04:36 PM, Craig Ringer wrote:
> On 5 January 2017 at 08:35, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> On 5 January 2017 at 01:49, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>>> Good. So we seem to agree that GUCS are transactional?
>>
>> No. We don't agree. They aren't.
>
> Uh. I take that back.
>
> craig=> SET x.s = 'x';
> SET
> craig=> BEGIN;
> BEGIN
> craig=> SET x.s = 'y';
> SET
> craig=> ROLLBACK;
> ROLLBACK
> craig=> SHOW x.s;
> x.s
> -----
> x
> (1 row)
>
>
> I'm surprised, I never knew this.
(I have not been able to keep up with the shear volume on this thread,
but this caught my eye...)
Yeah -- I found it surprising when I first discovered it too. My opinion
is that the design for variables should not behave this way.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-01-05 00:54:11 | Re: Replication slot xmin is not reset if HS feedback is turned off while standby is shut down |
Previous Message | Craig Ringer | 2017-01-05 00:36:32 | Re: proposal: session server side variables |