Re: Changing the state of data checksums in a running cluster

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Changing the state of data checksums in a running cluster
Date: 2024-10-01 18:55:34
Message-ID: B136F620-E386-49BC-BE04-4CE49FB3D323@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 1 Oct 2024, at 00:43, Michael Banck <mbanck(at)gmx(dot)net> wrote:
>
> Hi,
>
> On Mon, Sep 30, 2024 at 11:21:30PM +0200, Daniel Gustafsson wrote:
>>> Yeah, I think a view like pg_stat_progress_checksums would work.
>>
>> Added in the attached version. It probably needs some polish (the docs for
>> sure do) but it's at least a start.
>
> Just a nitpick, but we call it data_checksums about everywhere, but the
> new view is called pg_stat_progress_datachecksums - I think
> pg_stat_progress_data_checksums would look better even if it gets quite
> long.

That's a fair point, I'll make sure to switch for the next version of the
patch.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2024-10-01 18:55:48 Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
Previous Message Shayon Mukherjee 2024-10-01 18:17:19 Re: Proposal to Enable/Disable Index using ALTER INDEX