Re: Statement-level rollback - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Statement-level rollback
Date
Msg-id 20190131123827.pflxwlxonv46vjs4@alap3.anarazel.de
Whole thread Raw
In response to Re: Statement-level rollback  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Statement-level rollback  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018-12-08 17:55:03 -0300, Alvaro Herrera wrote:
> 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.

Is this still in development? Or should we mark this as returned with
feedback?

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables
Next
From: Yugo Nagata
Date:
Subject: Re: Implementing Incremental View Maintenance