Re: Reading recovery.conf earlier - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Reading recovery.conf earlier
Date
Msg-id 4B1D3641.7000803@enterprisedb.com
Whole thread Raw
In response to Re: Reading recovery.conf earlier  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Reading recovery.conf earlier  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> How does this sound?
> 
> At startup we will delete recovery.conf.running, if it exists.
> At startup recovery.conf will be copied to recovery.conf.running, which
> will be the file read by any additional processes that read
> recovery.conf during this execution. The permissions on the file will
> then be set to read-only.

Why not just follow the example of postresql.conf?

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Chris Browne
Date:
Subject: Re: Adding support for SE-Linux security
Next
From: Tom Lane
Date:
Subject: Re: Adding support for SE-Linux security