Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hqZ8N-0003An-30 for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Jul 2019 08:29:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hqZ8L-0000YT-Ko for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Jul 2019 08:29:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hqZ8L-0000Xy-7e for pgsql-hackers@lists.postgresql.org; Thu, 25 Jul 2019 08:29:53 +0000 Received: from [212.85.157.172] (helo=mail.dalibo.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1hqZ8I-00014J-2T for pgsql-hackers@postgresql.org; Thu, 25 Jul 2019 08:29:52 +0000 Received: from firost (abordeaux-656-1-241-32.w90-38.abo.wanadoo.fr [90.38.33.32]) by mail.dalibo.com (Postfix) with ESMTPSA id 093B01FBA4; Thu, 25 Jul 2019 10:29:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1564043386; bh=qtkNmmtjXBDcIQk3XzGrzfVTntpi7zKha54+jWzJTYI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=dvH9B1RHboLZnNcIIL0B1A5YZ0q8YBnTi81Tn74uCmpH0ry2AbRYMaChYuUXvOtQJ strCOR9muLiz1K7Ccs0gjQwKKQTdxWgK40wRp74+/09wudMNREe83pQiNfSFxRhOmz iApyz5syNPUE6/1ynj4vn2iuDWaSKXWhZNxEq4lw= Date: Thu, 25 Jul 2019 10:29:44 +0200 From: Jehan-Guillaume de Rorthais To: Michael Paquier Cc: Jesper Pedersen , PostgreSQL-development Subject: Re: pg_receivewal documentation Message-ID: <20190725102944.79a0be92@firost> In-Reply-To: <20190725075817.GA7647@paquier.xyz> References: <65c3ecdf-8995-34cb-83c4-50068877e632@redhat.com> <20190717013835.GA2130@paquier.xyz> <20190722014851.GC1757@paquier.xyz> <9fea76ce-6912-c262-6f64-2b7c4496be65@redhat.com> <20190723000820.GA2059@paquier.xyz> <72d2d628-eff9-94dc-8ced-0869bfda4e80@redhat.com> <20190724022928.GC14257@paquier.xyz> <20190724150304.02882f38@firost> <20190725075817.GA7647@paquier.xyz> Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 212.85.157.172 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, 25 Jul 2019 16:58:17 +0900 Michael Paquier wrote: > On Wed, Jul 24, 2019 at 03:03:04PM +0200, Jehan-Guillaume de Rorthais wrote: > > Unless I am missing something, another solution might be to use a dedicated > > role to pg_receive{xlog|wal} with synchronous_commit lower than > > remote_apply. > > Aren't you confused by the same thing as I was upthread [1]? > [1]: https://www.postgresql.org/message-id/20190710080423.GG1031@paquier.xyz > > remote_apply affects all sessions. So even if you use a replication > role with synchronous_commit = on and have pg_receivewal use that with > remote_apply set in postgresql.conf, then remote_apply is effective > for all the other sessions so these will still be stuck at commit > waiting for pg_receivewal to apply WAL if it is a synchronous > standby. Argh! (Sorry for the noise)