Tom Lane wrote:
> I'd view this as a postmaster state that propagates to backends.
> Probably you'd enable it by means of a postmaster option, and the
> only way to get out of it is to shut down and restart the postmaster
> without the option.
I've created a patch to make a postmaster read-only.
(attached patch can be applied to 8.0.1)
Read-only state can be enabled/disabled by the postmaster option,
or the postgresql.conf option.
If you start the postmaster with "-r" options,
the cluster will go to read-only.
% pg_ctl -o "-i -r" -D $PGDATA start
Or if you set "readonly_cluster = true" in the postgresql.conf,
the cluster will also become read-only.
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp
In response to
pgsql-hackers by date
|Next:||From: Ali Baba||Date: 2005-03-21 06:21:08|
|Subject: custome exception handling support ?|
|Previous:||From: Joshua D. Drake||Date: 2005-03-21 04:21:30|
|Subject: Re: Very strange query difference between 7.3.6 and 7.4.6|
pgsql-patches by date
|Next:||From: Neil Conway||Date: 2005-03-21 05:26:38|
|Subject: Re: [patch 0/6] pgcrypto update|
|Previous:||From: Tom Lane||Date: 2005-03-21 01:39:42|
|Subject: Re: PL/Python patch for Universal Newline Support |