Re: pg_system_identifier()
От | Greg Stark |
---|---|
Тема | Re: pg_system_identifier() |
Дата | |
Msg-id | CAM-w4HMJc+7OCDUFYD=ChWSp6jxBRPContr3Y2Y3py5swwaxig@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_system_identifier() (Hannu Krosing <hannu@2ndQuadrant.com>) |
Ответы |
Re: pg_system_identifier()
|
Список | pgsql-hackers |
<div dir="ltr">This doesn't generate a unique id. You could back up a standby and restore it and point it at the originalmaster and end up with two standbies with the same id.<br /></div><div class="gmail_extra"><br /><br /><div class="gmail_quote">OnFri, Aug 23, 2013 at 4:08 PM, Hannu Krosing <span dir="ltr"><<a href="mailto:hannu@2ndquadrant.com"target="_blank">hannu@2ndquadrant.com</a>></span> wrote:<br /><blockquote class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 08/22/2013 06:37PM, Tom Lane wrote:<br /> > A<br /> > Do we have a reliable way of generating a unique identifier for each slave<br/> > (independently of how that might be exposed)?<br /></div>Probably we could just generate an unique UUID whenwe first detect<br /> that we are replicating from the master with same UUID.<br /><br /> This of course requires thismaster UUID to be present in some way<br /> in the replication stream<br /><br /> Cheers<br /><span class="HOEnZb"><fontcolor="#888888"><br /> --<br /> Hannu Krosing<br /> PostgreSQL Consultant<br /> Performance, Scalabilityand High Availability<br /> 2ndQuadrant Nordic OÜ<br /></font></span><div class="HOEnZb"><div class="h5"><br /><br/><br /> --<br /> Sent via pgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br/> To make changes to your subscription:<br/><a href="http://www.postgresql.org/mailpref/pgsql-hackers" target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></div></div></blockquote></div><br /><br clear="all"/><br />-- <br />greg<br /></div>
В списке pgsql-hackers по дате отправления: