Re: [Patch] ALTER SYSTEM READ ONLY - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: [Patch] ALTER SYSTEM READ ONLY
Date
Msg-id CALj2ACVLfvqsjXQ18zSG_qaDAYNQ3-AvUQFDK_=CSRp0Cbye5Q@mail.gmail.com
Whole thread Raw
In response to Re: [Patch] ALTER SYSTEM READ ONLY  (Amul Sul <sulamul@gmail.com>)
Responses Re: [Patch] ALTER SYSTEM READ ONLY  (Amul Sul <sulamul@gmail.com>)
List pgsql-hackers
On Mon, Apr 5, 2021 at 11:02 AM Amul Sul <sulamul@gmail.com> wrote:
>
> Attached is the rebase version for the latest master head(commit # 9f6f1f9b8e6).

Some minor comments on 0001:
Isn't it "might not be running"?
+                 errdetail("Checkpointer might not running."),

Isn't it  "Try again after sometime"?
+                         errhint("Try after sometime again.")));

Can we have ereport(DEBUG1 just to be consistent(although it doesn't
make any difference from elog(DEBUG1) with the new log messages
introduced in the patch?
+    elog(DEBUG1, "waiting for backends to adopt requested WAL
prohibit state change");

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Masahiro Ikeda
Date:
Subject: Re: Why reset pgstat during recovery
Next
From: Masahiko Sawada
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies