Re: Feature Request: pg_replication_master()
От | Magnus Hagander |
---|---|
Тема | Re: Feature Request: pg_replication_master() |
Дата | |
Msg-id | CABUevEyPPOZdqw1OYd3SHq9f6PjNT==Nhz-RWW1d-cvjC2ONLg@mail.gmail.com обсуждение исходный текст |
Ответ на | Feature Request: pg_replication_master() (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Feature Request: pg_replication_master()
Re: Feature Request: pg_replication_master() |
Список | pgsql-hackers |
<p dir="ltr"><br /> On Dec 19, 2012 4:43 AM, "Josh Berkus" <<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br /> ><br /> > Hackers,<br /> ><br /> > Currentlywe can see each master's current replicas using<br /> > pg_stat_replication. However, there is no way from areplica, that I<br /> > know of, to figure out who its master is other than to look at<br /> > recovery.conf.<br />><br /> > We should probably have a function, like pg_replication_master(), which<br /> > gives the host addressof the current master. This would help DBAs for<br /> > large replication clusters a lot. Obviously, this wouldonly work in<br /> > streaming.<br /><p dir="ltr">This sounds like my previous suggestion of returning the primaryconninfo value, but with just ip. That one came with a pretty bad patch, and was later postponed until we folded recovery.confinto the main configuration file parsing. I'm not really sure what happened to that project? (the configurationfile one) <p dir="ltr">/Magnus
В списке pgsql-hackers по дате отправления: