Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p4h95-000711-SJ for pgsql-admin@arkaria.postgresql.org; Mon, 12 Dec 2022 11:38:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p4h94-0005Tm-FI for pgsql-admin@arkaria.postgresql.org; Mon, 12 Dec 2022 11:38:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p4Ti7-0004Fi-OH for pgsql-admin@lists.postgresql.org; Sun, 11 Dec 2022 21:18:12 +0000 Received: from 173-230-156-68.ip.linodeusercontent.com ([173.230.156.68] helo=nerf.kain.org) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p4Ti5-0006eN-Ba for pgsql-admin@lists.postgresql.org; Sun, 11 Dec 2022 21:18:11 +0000 Received: from [IPv6:::1] (unknown [IPv6:2605:a601:aea2:b700:e105:bb1:f583:b627]) by nerf.kain.org (Postfix) with ESMTPSA id 26745C157; Sun, 11 Dec 2022 21:18:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kain.org; s=20221110; t=1670793487; bh=GaP0tdqBBYuwrxGfkCIh/2Cju2omjeOusOfuxgXyI6o=; h=Date:From:To:Subject:In-Reply-To:References:From; b=PeHTihZ3DyKVc2eJZGCFooKj6Afb3hrQMwhphiMb0bUVb3P0Wqg9g9rNUOC/iXCQv KDz17TOrh8ufwiQ7rPYNaAZf3O84AeK986s1i41sQ1lE6BuiirweRfmcq6RLKjREOs bDBXHMzXd8/uzRWnIxoZ0RcacspkxiywpLkho3RNgoOerRJ2HmyunnlXoOoAN0nP+3 xEAjLgOWkxNH0i15TUOBqB5fKuLUHasP7gw07b+G0r0tsIwBZZ30YMukc6k5doyDlz o6BsgvdCV+6sEVnLAxIWN7wOIqHrb4PB03hjpxctankIuKdTvWl5KcV4von+XkngWl V/tgPkHventxQ== Date: Sun, 11 Dec 2022 21:18:06 +0000 From: =?ISO-8859-1?Q?Bryon_Roch=E9?= To: Laurenz Albe , Pgsql-admin Subject: Re: How to speed WAL apply in destination User-Agent: K-9 Mail for Android In-Reply-To: <44581ceb3c9c96f48e131ed3de33389db07317e9.camel@cybertec.at> References: <364439211.2445507.1670562179127.ref@mail.yahoo.com> <364439211.2445507.1670562179127@mail.yahoo.com> <1E6A35F6-6866-4FDB-8CE8-38C328FF1865@kain.org> <44581ceb3c9c96f48e131ed3de33389db07317e9.camel@cybertec.at> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On December 9, 2022 10:50:07 AM UTC, Laurenz Albe wrote: >On Fri, 2022-12-09 at 08:47 +0000, Bryon Roch=C3=A9 wrote: >> >> There are fsync parameters which can be set to off that may provide a m= odest speed increase, at the cost of removing crash safety=2E > >That is spectacularly bad advice=2E It is situational advice, and depending on your application, not bad advic= e at all=2E It is certainly not something you want off by default, or even = regularly=2E In fact, the PostgreSQL 15 (and earlier) versions cover this in the docume= ntation for the fsync and synchronous_commit parameters in section 20=2E5, = including considerations involved in deciding when to use those arameters, = along with further references in the documentation to cover more of the per= formance, synchronicity, and durability parameters, in detail=2E