| From: | Fabien COELHO <fabien(dot)coelho(at)mines-paristech(dot)fr> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| 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 09:59:26 |
| Message-ID: | alpine.DEB.2.20.1701051050530.3661@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> 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.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-01-05 10:04:09 | Re: proposal: session server side variables |
| Previous Message | Fabien COELHO | 2017-01-05 09:47:43 | Re: pgbench - allow to store select results into variables |