| From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | "'Joshua Berkus'" <josh(at)agliodbs(dot)com>, "'Simon Riggs'" <simon(at)2ndQuadrant(dot)com> |
| Cc: | "'PostgreSQL-development'" <pgsql-hackers(at)postgresql(dot)org>, "'Magnus Hagander'" <magnus(at)hagander(dot)net> |
| Subject: | Re: Feature Request: pg_replication_master() |
| Date: | 2012-12-20 04:52:43 |
| Message-ID: | 004201cdde6d$d9934000$8cb9c000$@kapila@huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, December 20, 2012 3:50 AM Joshua Berkus wrote:
>
> > 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 on the 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't we have
> something like that planned for SET PERSISTENT?
Yes in SET PERSISTENT patch, it uses "include_dir".
I wonder why can't we get this information from WALRcvData structure?
It has the required information.
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Groshev Andrey | 2012-12-20 04:55:16 | Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1 |
| Previous Message | Bruce Momjian | 2012-12-20 04:12:23 | Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1 |