From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: autonomous transactions |
Date: | 2016-09-08 05:36:53 |
Message-ID: | 20160908053653.kyr4nebycdxktvvf@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2016-08-30 21:50:05 -0400, Peter Eisentraut wrote:
> I would like to propose the attached patch implementing autonomous
> transactions for discussion and review.
>
> This work was mostly inspired by the discussion about pg_background a
> while back [0]. It seemed that most people liked the idea of having
> something like that, but couldn't perhaps agree on the final interface.
> Most if not all of the preliminary patches in that thread were
> committed, but the user interface portions were then abandoned in favor
> of other work. (I'm aware that rebased versions of pg_background
> existing. I have one, too.)
I kind of dislike this approach for a different reason than already
mentioned in this thread: Namely it's not re-usable for implementing
streaming logical replication of large transaction, i.e. allow to decode
& apply un-committed changes. The issue there is that one really needs
to have multiple transactions active in the same connection, which this
approach does not allow.
That's not necessarily a fatal objection, but I did want to throw that
as a design goal out there.
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2016-09-08 05:46:32 | Re: Parallel build with MSVC |
Previous Message | Amit Kapila | 2016-09-08 04:37:44 | Re: Write Ahead Logging for Hash Indexes |