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 1pVahM-0004hW-S1 for pgsql-general@arkaria.postgresql.org; Fri, 24 Feb 2023 16:13:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pVahL-0008Ri-Ok for pgsql-general@arkaria.postgresql.org; Fri, 24 Feb 2023 16:13:27 +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 1pVahK-0008RV-Li for pgsql-general@lists.postgresql.org; Fri, 24 Feb 2023 16:13:27 +0000 Received: from new3-smtp.messagingengine.com ([66.111.4.229]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVahH-00039S-Ga for pgsql-general@postgresql.org; Fri, 24 Feb 2023 16:13:26 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id 4D2C4581F8D; Fri, 24 Feb 2023 11:13:22 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 24 Feb 2023 11:13:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1677255202; x=1677262402; bh=h FptT709urtv+h1tZ2ltC/0heprUcxU0IW7T/H9gwbc=; b=aONfVuXVfrWoAKEIA mc5BjwUOax1/piRuNm0XAu1PCvWyos6RipWLB/1PZuQ1loGS4uUL4i5yrgb24YOT g4IfRKFjhCIjOMinCD7+78loaEX7F4x3ORzYzybNHwJUR3z5pxJUbbUrOLq+IZui TVVwkLSndW48ries/Nn/hVCTgXSWD2YdKSVIvBQFpOAFMpC43KYUOCPSGsiEVN/F V2mcUCKWVyhLeDG8uhbThvyrgogTLexlFWoA3LP6AJUkOmFgFmbhwYOYywvmD7ce ZB3iwt16P9uYjW1a0dGb+WwYjqeCZ1qyOFEX/k8PyInNp54srLkN3rCum5LR2O86 8zvHA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudekfedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeelgfetfeeitdelleeggeejvefhueetfedvtdejheevueeifeegvdfhueel udetueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 24 Feb 2023 11:13:21 -0500 (EST) Message-ID: Date: Fri, 24 Feb 2023 17:13:20 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: PostgreSQL optimizations for CoW FS Content-Language: de-DE To: HECTOR INGERTO , "pgsql-general@postgresql.org" References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22.02.23 10:41, HECTOR INGERTO wrote: > Let’s say we have to run a PostgreSQL instance on top of a copy on write > filesystem like ZFS or BTRFS. In adittion to set full_page_writes = off, > what other optimizations can be done on the PostgreSQL side? Look at the settings wal_init_zero and wal_recycle.