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 1u5tK8-007bBL-DZ for pgsql-general@arkaria.postgresql.org; Fri, 18 Apr 2025 21:32:36 +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 1u5tK6-002bwx-CR for pgsql-general@arkaria.postgresql.org; Fri, 18 Apr 2025 21:32:35 +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 1u5tK6-002bwn-0M for pgsql-general@lists.postgresql.org; Fri, 18 Apr 2025 21:32:34 +0000 Received: from mail-oi1-x22f.google.com ([2607:f8b0:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u5tK3-000ldQ-27 for pgsql-general@postgresql.org; Fri, 18 Apr 2025 21:32:33 +0000 Received: by mail-oi1-x22f.google.com with SMTP id 5614622812f47-3fea0363284so1299740b6e.1 for ; Fri, 18 Apr 2025 14:32:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1745011951; x=1745616751; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W9w8PouWhzVaX8DUiBC+3XqrmxiQy5YqIBcrwpbycvc=; b=JMMI55LWzkqjLdFAAYveZC72uFnoFLxWQewvDIE/0J7t+y8GTvw6zo7Ma7aBJ2MJpk OnfvfnHz6BgwOfQiD4E5ExDdUrLYyXNe0W/ejdhcI8GY+6YGBNQAT190i0YsV0/ev4uB vUH0YoqR/qhV6eXSPrwgtT8KdfH/vfJKpYMnR6px9CSvyu/DdarS4eLSdmH9svTP9aIb lJhOuFfOrGlXv8yKoEr6QSENBkp3jqj8ChliFd3KN1x/etbxJV9GTlGJPLJDqcu/zLfk n/K1xfye+IKcy8shTtEHZe6DYrZsPl3qUmbuN+r0HOLR1qmAkZs79bkJmjqbZR0gSHsO M7vQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745011951; x=1745616751; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W9w8PouWhzVaX8DUiBC+3XqrmxiQy5YqIBcrwpbycvc=; b=a6eYZnpyiwJsblHUojfI9pqyVV4WtQy2E69VbR5xFxXCAu1eNvYXdKnPiZ0h7wTOzX 21uc8sqPD+rdgzXA7SjzP+Qjmu4lXUu3gZiicjxqAix1/aYis/fBf6dejV9YxgXhtgzB epv41UEXN2Gb3IPTl6YbO0X1nqHXdd6g5HpudFC3ZbSGVJR2ZwNTYfMx34ekYQTJB4Lx xC/d2QhMjyX6th6I3WfrRyN58S/Mz1XQhHjWWmI2OGPK7XXBNYLz1EN86pZMH1tLuKHr w0jLb0nbvU8r8xmsHuGxhpJad1Utep6pwF+0bEXOR5KCMOwbdkmLD1v312lQj4hax15t jI6g== X-Gm-Message-State: AOJu0YzCGZQ++lghl1XVE5DJWV+hqdL7WFB6vfac/ZWB2xBV1scxja+h iA3DoortZ7UmlaguxvF1cK8xl3Q3vrpBZ6ovwan/pjSK07MyhMrbAXIP6AolgwJjF4JUoTuZlxl MTRcJqBxbY1Js/5jV3341s7s0ihM= X-Gm-Gg: ASbGncvKdbP5c1HUlD1PXQFEIGdDplYBUINYXVLFku51oA+Tmusd/uJPfuwtgkFAfFF pIDOBeoEpuCG2dvFixIlnYMPLwDK9cr8jYqmYPSwl1LTpkYHNjeiT5BuukgjiOtgPkVUzFmZyrO H5DEysSTDsSpdIM1PxgSWzPEnVTUIPV9GyEvJqgQ0yzgtlUur7hPkplNHU X-Google-Smtp-Source: AGHT+IFQDc2xOJFlHS4nfdPiEWRCku2YbOvOFFd3wZGrIfEAXWQ7FPM3GbVTdOviDHPT3eqg128+3tPFUm77MPk5E1I= X-Received: by 2002:a05:6808:850c:b0:3f4:bc5:d47a with SMTP id 5614622812f47-401c0ad1e04mr2138155b6e.13.1745011950907; Fri, 18 Apr 2025 14:32:30 -0700 (PDT) MIME-Version: 1.0 References: <20250418141817.2457ac8d@ardentperf.com> In-Reply-To: <20250418141817.2457ac8d@ardentperf.com> From: Ron Johnson Date: Fri, 18 Apr 2025 17:32:19 -0400 X-Gm-Features: ATxdqUF_YNZm3yEX11-lC4vO81MU_t-Nt-znWh9sf4aUdIUbfTdjdJC_WLzrrbs Message-ID: Subject: Re: verify checksums online To: Jeremy Schneider Cc: "pgsql-general@postgresql.org" Content-Type: multipart/alternative; boundary="0000000000007679ee06331441b1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007679ee06331441b1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 18, 2025 at 5:18=E2=80=AFPM Jeremy Schneider wrote: > i should know the answer to this... but asking anyway > > i think there had been some mailing list discussions years ago? the > pg_checksum utility in core still can't do an online check right? > https://www.postgresql.org/docs/17/app-pgchecksums.html "The server must be shut down cleanly before running pg_checksums." > looking around, i think that michael's pg_checksums_ext still seems to > be available in debian repos, and it advertises online checks, which > makes me think that the core pg_checksum might still not have merged > any code for online checking yet > > but i wanted to confirm with someone - my easiest options for online > verifying checksums would be to trigger pg_basebackup then check > pg_stat_database, or to install michael's utility? > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000007679ee06331441b1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Apr 18, 2025 at 5:18=E2=80=AFPM J= eremy Schneider <schneider@a= rdentperf.com> wrote:
i should know the= answer to this... but asking anyway

i think there had been some mailing list discussions years ago? the
pg_checksum utility in core still can't do an online check right?


"The server must= be shut down cleanly before running=C2=A0pg_checksums."
=C2=A0
looking around, i think that michael's pg_checksum= s_ext still seems to
be available in debian repos, and it advertises online checks, which
makes me think that the core pg_checksum might still not have merged
any code for online checking yet

but i wanted to confirm with someone - my easiest options for online
verifying checksums would be to trigger pg_basebackup then check
pg_stat_database, or to install michael's utility?

--
Death to <Redacte= d>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
--0000000000007679ee06331441b1--