Re: [ADMIN] pg_basebackup blocking all queries with horrible performance

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Lonni J Friedman <netllama(at)gmail(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Jerry Sievers <gsievers19(at)comcast(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] pg_basebackup blocking all queries with horrible performance
Date: 2012-06-20 11:58:32
Message-ID: CA+U5nM+SGGr02xLLCCppjw2Y4q1Lnb35rtuGyNkoCjdo=aUsog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 11 June 2012 23:47, Magnus Hagander <magnus(at)hagander(dot)net> wrote

>> You agreed to add something like NOSYNC option into START_REPLICATION command?
>
> I'm on the fence. I was hoping somebody else would chime in with an
> opinion as well.

Why would you add it to synchronous_standby_names and then explicitly ignore it?

I don't see why you'd want this.

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Simon Riggs 2012-06-20 12:02:57 Re: pg_basebackup blocking all queries with horrible performance
Previous Message Magnus Hagander 2012-06-20 11:18:23 Re: [ADMIN] pg_basebackup blocking all queries with horrible performance

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-06-20 12:02:57 Re: pg_basebackup blocking all queries with horrible performance
Previous Message Dickson S. Guedes 2012-06-20 11:35:05 Re: Release versioning inconsistency