Re: Synchronous commit not... synchronous? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Synchronous commit not... synchronous?
Date
Msg-id CA+U5nM+e6C6Gm9Xn48k3_oU5C9a=7qYcC=yscvPUZ5VsqcD8AA@mail.gmail.com
Whole thread Raw
In response to Re: Synchronous commit not... synchronous?  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Synchronous commit not... synchronous?  (Shaun Thomas <sthomas@optionshouse.com>)
Re: Synchronous commit not... synchronous?  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
On 2 November 2012 16:27, Jeff Janes <jeff.janes@gmail.com> wrote:
> On Thu, Nov 1, 2012 at 12:42 PM, Daniel Farina <daniel@heroku.com> wrote:
>> On Wed, Oct 31, 2012 at 10:10 PM, Michael Paquier
>> <michael.paquier@gmail.com> wrote:
>>> Btw, I believe that this is correct behavior, because in Peter's case the
>>> manual command gets the priority on the value of synchronous_commit, no?
>>> If anybody thinks that I am wrong, feel free to argue on that of course...
>>
>> The idea of canceling a COMMIT statement causing a COMMIT seems pretty
>> strange to me.
>
> It would be.  But you are not cancelling the commit, you are
> *attempting* to cancel the commit.  The message you receive explains
> to what extend your attempt succeeded.

That is correct.

It is possible to cancel the COMMIT, but only until it happens.

If people want full two phase commit, that option exists also.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Incorrect behaviour when using a GiST index on points
Next
From: Shaun Thomas
Date:
Subject: Re: Synchronous commit not... synchronous?