| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_checksums docs mentioning online functions |
| Date: | 2026-06-04 21:08:26 |
| Message-ID: | aiHpSr23DmL1w71c@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Jun 4, 2026 at 10:39:53PM +0200, Daniel Gustafsson wrote:
> > On 4 Jun 2026, at 22:12, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > My big issue is that we explain the limitation of pg_checksums, but
> > don't point readers at the tool that doesn't have that offline
> > restriction. I think we need that explicitly mentioned, and at the top.
>
> How about something like the attached?
Looks good, just one suggestion:
> + When enabling checksums with <application>pg_checksums</application>, if
> + checksums were in the process of being enabled using
> + <xref linkend="checksums-online-enable-disable"/> when the cluster was shut
> + down, <application>pg_checksums</application> will still process all relation
> + files regardless of progress of the online processing.
... pg_checksums will still process all relation files regardless of
the progress of online checksum processing.
-------------------------------
I think this idea is complex enough that we have to clearly state
"online _checksum_ processing."
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-06-04 22:21:41 | Re: pg_checksums docs mentioning online functions |
| Previous Message | Daniel Gustafsson | 2026-06-04 20:39:53 | Re: pg_checksums docs mentioning online functions |