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 1qx7WS-00GAjv-DB for pgsql-general@arkaria.postgresql.org; Sun, 29 Oct 2023 15:16:16 +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 1qx7WR-007lwz-1e for pgsql-general@arkaria.postgresql.org; Sun, 29 Oct 2023 15:16:15 +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 1qx7WQ-007lwq-Mt for pgsql-general@lists.postgresql.org; Sun, 29 Oct 2023 15:16:14 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qx7WN-002uCX-BG for pgsql-general@lists.postgresql.org; Sun, 29 Oct 2023 15:16:13 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-53d9f001b35so5766333a12.2 for ; Sun, 29 Oct 2023 08:16:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698592568; x=1699197368; darn=lists.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=zoR0ikMx+7OB/2Ojb+6YH68Z3Ddh0uAsFQzRVg2o7R0=; b=RC5wPeEZ1faSUJ2PIQ4/SZKMgkehpf/lNbjZe18pig2KmhhYPE3XQcgdhfSjjz5d+2 rwb5G6ZJEvl5UQHKuKdNtaoRdzsZ5kQwfl6dqcpZjlKr788RnZ2IULz2OculHzUJ5XaY JlG4SSyp2Uww1B9UcVX1nNdDW4fdwXyCJDtFIw2MP5aLQaKapFqjlJR0AeK5K/fHDhYZ oWOfb6AdrGOohgYdgsB4u0h8HPMNJcQDM5/cHo5XDJJRpg0qtRray5mESdjTnwUimM55 xJY2x1ToBe1SnVovVg+Crdd9KqcGuOG7ftHjEXuEWSM6RT1xnDf1PVKMSlR3JCHfGq71 zHFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698592568; x=1699197368; 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=zoR0ikMx+7OB/2Ojb+6YH68Z3Ddh0uAsFQzRVg2o7R0=; b=Y7cBl8XBGU6CUTwCxrO0EXaE9VZqoURPv5UXKnqgjYatXKyfa9M6sh3YSmCsjEks+g 0wigLcCONcJbEzVSSy80CAUDeNAF2XDfE1BuP8HdbL8Gvl2PZAbrgrXYgpw+nm9WQzpQ JDlxKkg5mdvkwVh+ZCqMG9iyPyk7e40E/GyNWNJZP/0wx9+hTLsYjEG7yzFlo/eXjUP+ dp02naueechqlzPPz7MYZsJBcpVPvGfsD0DEJ1fFPbadrhUZt0wmSpHFfpYXpoGeaucg x/KDcKsDaaYQ+Fqsehbau+HAFUeeg7DdFDjVx5HLJUYwrhRJWnL/OxqGq87GYAhAvPqI U7Vw== X-Gm-Message-State: AOJu0Yw9mG/vU1HFmzfShns50zLLM5WXt6wb7jdodjc3r6vZKxhWs6eB d5jTDvsUxmhWHOBvrpNMkys= X-Google-Smtp-Source: AGHT+IE9DYL63pFiTCZOsaESaBbo34XjioZ3d6+TR4gDMIIPraRYC16hSoSAu8YNIqfd/ObvJ+MCqg== X-Received: by 2002:a17:906:4787:b0:9b2:b786:5e9c with SMTP id cw7-20020a170906478700b009b2b7865e9cmr6171722ejc.28.1698592568165; Sun, 29 Oct 2023 08:16:08 -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 x22-20020a170906149600b009b2b47cd757sm4411540ejc.9.2023.10.29.08.16.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 29 Oct 2023 08:16:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii 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: <20231029104911.dj73ivozabdr5or4@hjp.at> Date: Sun, 29 Oct 2023 16:15:37 +0100 Cc: pgsql-general@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <4614561A-6176-4136-BA96-74B05A7B6B5C@gmail.com> References: <22272207-E6E5-4DD5-9BD4-5F6B647E2C3B@gmail.com> <0D18D31E-EF52-434D-875C-08BEC8DDD553@yesql.se> <20231029014310.7pbdfhincj2tds4l@hjp.at> <81D43A87-7D3D-4F81-B462-641F15B5E332@gmail.com> <20231029104911.dj73ivozabdr5or4@hjp.at> To: "Peter J. Holzer" 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 Peter, > On Oct 29, 2023, at 11:49, Peter J. Holzer wrote: >=20 > It *might* work if there are zero writes on the primary during the > downtime of the replica (because those writes couldn't be replicated), > but that seems hard to ensure. Even if you could get away with making > the primary read-only (is this even possible?) I wouldn't have much > confidence in the result and reinit the (new) replica anyway. As soon as I stop the replica to enable checksums, even writes can't get = replicated anymore. So during enabling checksums, a replica is = definitely protected against modifications by its primary, simply = because it's down. The modifications of the primary are applied to the = replica when it comes back online. So, I don't see a problem at this = particular stage. My fear is merely that enabling checksums does something to the physical = state of the data files which are not compatible with the other side. = Like for example manipulate the file headers in some way. Maybe this question is better suited for the admin list than this = general list? Cheers Paul=