| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Subject: | Re: Statement-level rollback |
| Date: | 2018-12-08 20:10:27 |
| Message-ID: | 20181208201027.qhz5jvvhbdlwwehj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Dec-07, Andres Freund wrote:
> I think it could partially be addressed by not allowing to set it on the
> commandline, server config, etc. So the user would have to set it on a
> per-connection basis, potentially via the connection string.
This is what patch 0001 does -- it's only allowed in the connection
string, or on ALTER USER / ALTER DATABASE. Setting it in
postgresql.conf is forbidden, as well as changing from transaction to
statement in SET (the opposite is allowed, though.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-12-08 20:31:04 | Re: Statement-level rollback |
| Previous Message | Pavel Stehule | 2018-12-08 20:05:16 | proposal: new polymorphic types - commontype and commontypearray |