Re: Feature Request: pg_replication_master() - Mailing list pgsql-hackers

From Joshua Berkus
Subject Re: Feature Request: pg_replication_master()
Date
Msg-id 2135840391.118788.1355955594429.JavaMail.root@agliodbs.com
Whole thread Raw
In response to Re: Feature Request: pg_replication_master()  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Feature Request: pg_replication_master()
Re: Feature Request: pg_replication_master()
List pgsql-hackers
> It stalled because the patch author decided not to implement the
> request to detect recovery.conf in data directory, which allows
> backwards compatibility.

Well, I don't think we had agreement on how important backwards compatibility for recovery.conf was, particularly not
onthe whole recovery.conf/recovery.done functionality and the wierd formatting of recovery.conf.
 

However, with "include_if_exists" directives in postgresql.conf, or "include_dir", that would be easy to work around.
Don'twe have something like that planned for SET PERSISTENT?
 

--Josh Berkus



pgsql-hackers by date:

Previous
From: Joshua Berkus
Date:
Subject: Re: Cascading replication: should we detect/prevent cycles?
Next
From: Joshua Berkus
Date:
Subject: Re: Feature Request: pg_replication_master()