Skip site navigation (1) Skip section navigation (2)

Re: Synchronous commit not... synchronous?

From: David Fetter <david(at)fetter(dot)org>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Peter van Hardenberg <pvh(at)pvh(dot)ca>,"pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Synchronous commit not... synchronous?
Date: 2012-11-01 04:48:13
Message-ID: 20121101044813.GD625@fetter.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Nov 01, 2012 at 01:31:34PM +0900, Michael Paquier wrote:
> On Thu, Nov 1, 2012 at 1:03 PM, David Fetter <david(at)fetter(dot)org> wrote:
> > On Wed, Oct 31, 2012 at 06:39:20PM -0700, Peter van Hardenberg wrote:
> > > This was rather surprising - my synchronous commit was... not
> > > cancelled.  Is this expected behaviour?
> >
> > I believe it is.
> >
> > Does the following do the right thing?
> >
> > SET synchronous_commit='on';
> > BEGIN;
> > INSERT INTO data VALUES ('baz');
> > COMMIT;^c
> >
> > Oh, and how did you get that cancel in?
> >
> He enforced a manual cancel from client with something like Ctrl+C to
> cancel query.
> In this case you do not wait for the slave to confirm that the commit
> information has been flushed on its disk.

I guess my disk subsystem (it's a consumer-grade DAS SSD) doesn't have
enough latency for my reflexes to hit ^C fast enough.  Any way to
inject this fault deterministically?

Cheers,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


In response to

Responses

pgsql-hackers by date

Next:From: Michael PaquierDate: 2012-11-01 05:10:46
Subject: Re: Synchronous commit not... synchronous?
Previous:From: Michael PaquierDate: 2012-11-01 04:31:34
Subject: Re: Synchronous commit not... synchronous?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group