On Sat, Jun 9, 2012 at 2:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
>> This seems a bug. I think we should prevent pg_basebackup from
>> becoming synchronous standby. Thought?
> Absolutely. If we have replication clients that are not actually
> capable of being standbys, there *must* be a way for the master
> to know that.
I thought we fixed this already by sending InvalidXlogRecPtr as flush
location? And that this only applied in 9.2?
Are you saying we picked pg_basebackup *in backup mode* (not log
streaming) as synchronous standby? If so then yes, that is
*definitely* a bug that should be fixed. We should never select a
connection that's not even streaming log as standby!
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2012-06-10 10:55:32|
|Subject: Re: pg_receivexlog and feedback message|
|Previous:||From: Magnus Hagander||Date: 2012-06-10 10:23:31|
|Subject: Re: incorrect handling of the timeout in pg_receivexlog|
pgsql-admin by date
|Next:||From: Fujii Masao||Date: 2012-06-10 12:25:38|
|Subject: Re: pg_basebackup blocking all queries with horrible performance|
|Previous:||From: Edson Richter||Date: 2012-06-10 02:59:57|
|Subject: Re: is there a select for update insert if not exist type