Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannot be changed later", but *can* be in Pg 12.

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: basil(dot)bourque(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15909: Doc for `initdb` on `--data-checksums` says "cannot be changed later", but *can* be in Pg 12.
Date: 2019-07-17 07:57:56
Message-ID: 50ABC76E-7BA7-47DD-A5F8-5327B80D5C60@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 17 Jul 2019, at 05:30, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 16, 2019 at 04:10:52PM +0000, PG Bug reporting form wrote:
>> But now in Postgres 12, the `pg_checksums` command can enable or disable
>> checksums on an existing cluster.
>
> My fault here. As it is an initdb option, it is pretty obvious that
> it is an initialization-time option. My take is to simply remove the
> sentence completely instead of adding an extra reference to
> pg_checksums. Thoughts?

Agreed, better to just remove the sentence altogether.

cheers ./daniel

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Manuel Rigger 2019-07-17 12:53:54 REINDEX CONCURRENTLY causes ALTER TABLE to fail
Previous Message Fahar Abbas 2019-07-17 05:41:31 Re: PLEASE HELP!