From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: chained transactions |
Date: | 2018-03-05 09:21:33 |
Message-ID: | CANP8+jLDje=KLh_R7_Nv=_=18sWyNAGOLFLiXMZC1zcDAdTzJw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2 March 2018 at 07:18, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-02-28 22:35:52 -0500, Peter Eisentraut wrote:
>> This feature is meant to help manage transaction isolation in
>> procedures.
>
> This is a major new feature, submitted the evening before the last CF
> for v11 starts. Therefore I think it should just be moved to the next
> fest, it doesn't seems realistic to attempt to get this into v11.
Looks like a useful patch that adds fairly minor syntax that follows
the SQL Standard.
It introduces no new internal infrastructure, so I can't call this a
major feature.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2018-03-05 09:42:27 | Re: GSOC 2018 ideas |
Previous Message | Pavan Deolasee | 2018-03-05 09:04:02 | Re: ON CONFLICT DO UPDATE for partitioned tables |