| 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:55:03 |
| Message-ID: | 20181208205503.sw3ohupigf4uznwy@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Dec-08, Andres Freund wrote:
> On 2018-12-08 17:10:27 -0300, Alvaro Herrera wrote:
> > 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.)
>
> I don't think allowing to set it on a per-user basis is acceptable
> either, it still leaves the client in a state where they'll potentially
> be confused about it.
Hmm, true.
> Do you have a proposal to address the issue that this makes it just
> about impossible to write UDFs in a safe way?
Not yet, but I'll give it a think next week.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-12-08 23:15:07 | Re: pg_partition_tree crashes for a non-defined relation |
| Previous Message | Andres Freund | 2018-12-08 20:31:04 | Re: Statement-level rollback |