Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwUWn-00C6o0-VG for pgsql-general@arkaria.postgresql.org; Fri, 27 Oct 2023 21:38:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qwUWm-001YHt-F9 for pgsql-general@arkaria.postgresql.org; Fri, 27 Oct 2023 21:38:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qwUWm-001YHi-4J for pgsql-general@lists.postgresql.org; Fri, 27 Oct 2023 21:38:00 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qwUWj-002dL4-Bw for pgsql-general@postgresql.org; Fri, 27 Oct 2023 21:37:58 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9bdf5829000so413778566b.0 for ; Fri, 27 Oct 2023 14:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698442676; x=1699047476; darn=postgresql.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lm7qHZ3WRuXthhAdR13BOEXcYVgWhAUD5jDO8Hd1OoY=; b=dcXi2H0WyNSreTPs3izFYIK12fJkgnSeA1PuL0abe5+UnOZLCxCdHMIeHQLk8UU2ng M52ButekZwnnR8Fe2HtmoIptswSPQJs2k1I9DgWHOYGxvsSz63WgC4rXU2XGGyJhrZne c/kj5+jbDtqv2LNhZna2unLD/xuerCJphPUi3E0kem5y9zqxP+oK7b4/CayiT6VYlVO7 pvavqLhmQ2O+RkBaUUOazt05TvvW/q7o8s1HI6I+ncTMrvNnAAmve9XnliqIhoslpxIX +qlXkthU0H6jBjTxXUK05Y/g9VrOahoyNztkHvG6WozpG1DVNS76dkLVdxgnJBYhpiHt Uy9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698442676; x=1699047476; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=lm7qHZ3WRuXthhAdR13BOEXcYVgWhAUD5jDO8Hd1OoY=; b=gAOPs/7tRCzks0d2S2x2J6RK+A/DQ3LJ/mCf/G8EQ91ovGfwGQly7YumP0oPvDS/kt xL5yiTFXv9RjGz5rK/aSPcHBsIwcjVmktSEJg5jobx8jg7vS4UsmPIMNljM7Wq9D7kZb O93w+rfk7GIGWV0OUOEEdh7Pa1q6BmTytUIcceKthETLu+SsC/uLLen+bz2OOMSiI2t3 GqJO0lfVbWbh+Z2HjX3RpTiIurufq/pw/Mb3VVWruX3oBpR5Hs/IW1S/jtKRGw2xHsQI E2IlR5UKFWXnI441A7/jcpR4E76kqUvYIbrg5dhjcHdGasGO6AWwmosVL/TNnWrymKX9 87Lg== X-Gm-Message-State: AOJu0YxmGcFoj0lj88OzqaljEG+VE4s6NxLX1By5uzz1H8ITtF2sq2zR ZODEv9XoHXCyshaY31PnOi4= X-Google-Smtp-Source: AGHT+IGXbpIodePk3lnScTxHQihdnQwfJFH4zwbYhaK1Yev3cOqCy8iOOVIxiIdCwdnD/c4fWPGgow== X-Received: by 2002:a17:907:96a5:b0:9be:5ab2:73c0 with SMTP id hd37-20020a17090796a500b009be5ab273c0mr2947775ejc.8.1698442675621; Fri, 27 Oct 2023 14:37:55 -0700 (PDT) Received: from smtpclient.apple (26-36-239-77.dyn.cable.fcom.ch. [77.239.36.26]) by smtp.gmail.com with ESMTPSA id cf17-20020a170906b2d100b00997d7aa59fasm1779030ejb.14.2023.10.27.14.37.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Oct 2023 14:37:55 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: pg_checksums? From: =?utf-8?Q?Paul_F=C3=B6rster?= In-Reply-To: Date: Fri, 27 Oct 2023 23:37:24 +0200 Cc: Daniel Gustafsson , "pgsql-general@postgresql.org >> PG-General Mailing List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <22272207-E6E5-4DD5-9BD4-5F6B647E2C3B@gmail.com> <0D18D31E-EF52-434D-875C-08BEC8DDD553@yesql.se> To: Bruce Momjian X-Mailer: Apple Mail (2.3774.200.91.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Bruce, hi Daniel, > On Oct 27, 2023, at 23:21, Bruce Momjian wrote: >=20 > On Fri, Oct 27, 2023 at 10:45:16PM +0200, Daniel Gustafsson wrote: >>> On 27 Oct 2023, at 20:34, Paul F=C3=B6rster = wrote: >>=20 >>> a) why isn't it possible to enable checksumming while a database = cluster is up? >>=20 >> It is surprisingly complicated to enable checksums on a live cluster, = a patch >> was submitted a while back but ultimately never made it into = postgres. The >> below threads may shine some light on the problem: >>=20 >> = https://www.postgresql.org/message-id/flat/CABUevEx8KWhZE_XkZQpzEkZypZmBp3= GbM9W90JLp%3D-7OJWBbcg%40mail.gmail.com >> = https://www.postgresql.org/message-id/flat/560A2239-5DE2-4B9C-92BC-878C682= 2F47C%40yesql.se#10b665b2193445a3d7f24be7917a952c >=20 > Yeah, it was a big surprise that this feature was so hard to implement > because we have _no_ infrastructure for having multiple data layouts > active in a live system. The discussion eventually made that clear. >=20 > If we have more features that need this kind of dynamic ability, we > might revisit this feature too. Ok, I see. But unfortunately still, my questions c) and d) are unanswered. I'd = especially be interested in an answer to c), i.e. is it *safe* to = "pg_checksum -e" the replica instance in a patroni cluster, switch over, = and then do the other one? Cheers Paul