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

From tushar
Subject Re: [Patch] ALTER SYSTEM READ ONLY
Date
Msg-id e974a552-3e3e-c735-5179-7708dfa26ffb@enterprisedb.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
Re: [Patch] ALTER SYSTEM READ ONLY
List pgsql-hackers
On 6/22/20 11:59 AM, Amul Sul wrote:
> 2. Now skipping the startup checkpoint if the system is read-only mode, as
> discussed [2].

I am not able to perform pg_checksums o/p after shutting down my server 
in read only  mode .

Steps -

1.initdb (./initdb -k -D data)
2.start the server(./pg_ctl -D data start)
3.connect to psql (./psql postgres)
4.Fire query (alter system read only;)
5.shutdown the server(./pg_ctl -D data stop)
6.pg_checksums

[edb@tushar-ldap-docker bin]$ ./pg_checksums -D data
pg_checksums: error: cluster must be shut down
[edb@tushar-ldap-docker bin]$

Result - (when server is not in read only)

[edb@tushar-ldap-docker bin]$ ./pg_checksums -D data
Checksum operation completed
Files scanned:  916
Blocks scanned: 2976
Bad checksums:  0
Data checksum version: 1

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company




pgsql-hackers by date:

Previous
From: "Inoue, Hiroshi"
Date:
Subject: Re: Removal of currtid()/currtid2() and some table AM cleanup
Next
From: Daniel Gustafsson
Date:
Subject: Re: should libpq also require TLSv1.2 by default?