Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id E98671EA2927 for ; Sat, 9 Jun 2012 09:51:31 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SdL8b-0002V2-0g for pgsql-admin@postgresql.org; Sat, 09 Jun 2012 12:51:31 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q59CpAu2026789; Sat, 9 Jun 2012 08:51:10 -0400 (EDT) From: Tom Lane To: Fujii Masao cc: Lonni J Friedman , Craig Ringer , Jerry Sievers , Magnus Hagander , pgsql-admin@postgresql.org Subject: Re: pg_basebackup blocking all queries with horrible performance In-reply-to: References: <874nqmy8cj.fsf@comcast.net> <4FD195F9.8080108@ringerc.id.au> Comments: In-reply-to Fujii Masao message dated "Sat, 09 Jun 2012 11:29:36 +0900" Date: Sat, 09 Jun 2012 08:51:10 -0400 Message-ID: <26788.1339246270@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201206/45 X-Sequence-Number: 39636 Fujii Masao 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. regards, tom lane