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 05:24:26 |
Message-ID: | 20121101052426.GE625@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 01, 2012 at 02:10:46PM +0900, Michael Paquier wrote:
> On Thu, Nov 1, 2012 at 1:48 PM, David Fetter <david(at)fetter(dot)org> wrote:
>
> > 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?
> >
> If the point is to get this warning, you can always setup
> synchronous_standby_names with the application name of a slave that is not
> listed in pg_stat_replication to make the master hanging for a slave that
> does not exist :)
> But in this case there is virtually no slave to wait for, so perhaps it has
> no meaning... But it lets you all time you want to do a manual cancel and
> get this warning.
Great idea :)
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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit kapila | 2012-11-01 07:35:04 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |
Previous Message | Michael Paquier | 2012-11-01 05:10:46 | Re: Synchronous commit not... synchronous? |