Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCszH-0002zX-Gn for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Aug 2013 15:09:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VCszG-000733-R3 for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Aug 2013 15:09:18 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCsyD-0005cl-P1 for pgsql-hackers@postgresql.org; Fri, 23 Aug 2013 15:08:13 +0000 Received: from moutng.kundenserver.de ([212.227.126.186]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCsyA-00063t-SX for pgsql-hackers@postgresql.org; Fri, 23 Aug 2013 15:08:13 +0000 Received: from [192.168.11.106] (62.175.246.114.static.riosat.com [62.175.246.114]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0M852L-1Vz3ji0jwH-00vPLM; Fri, 23 Aug 2013 17:08:07 +0200 Message-ID: <52177AD5.5010809@2ndQuadrant.com> Date: Fri, 23 Aug 2013 17:08:05 +0200 From: Hannu Krosing Organization: 2ndQuadrant Nordic =?ISO-8859-1?Q?O=DC?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8 MIME-Version: 1.0 To: Tom Lane CC: Andres Freund , Alvaro Herrera , Josh Berkus , pgsql-hackers@postgresql.org Subject: Re: pg_system_identifier() References: <5215346B.7070800@dalibo.com> <20130822134205.GC17006@awork2.anarazel.de> <52163222.9030700@agliodbs.com> <20130822155633.GF17006@awork2.anarazel.de> <14611.1377187563@sss.pgh.pa.us> <20130822161839.GG17006@awork2.anarazel.de> <20130822162019.GC10710@eldon.alvh.no-ip.org> <20130822163059.GI17006@awork2.anarazel.de> <15653.1377189456@sss.pgh.pa.us> In-Reply-To: <15653.1377189456@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:6thv09bKHzLjGXR1uazfmltjyOuK4XZG9bDbui2JoQs NzCda/GWzCmgslWL68UJ4wW+ZYSJPIz1BtlciU1z+oexnh8664 wdjR8alwFvVihgkcwNHspcBcBrZ1zvK9W72g1AmwyDqMZTX0hw YQX2Lo+ZWwY6pZBXXi2eQw4sDUXaeUrdSHsOo7dt3/njUn2QYe 9gi+b/SOw2CfNpA1Cc+i0Q86sdVguMRJeT7rF/MNpXr1gu8+Ul 4vfRofdnZgJ5dnMMRUudEZAXhgQQt8gCNUPWb3PDjHcX2TYgBg YpiUE2BvI1msliIa2KOxdUw2K6oshsoh5nr/VHtq8m/O0bfO00 XQ98ekOhCe7NFKTN7PozpnLlTCdAuqFqFs8IYenzj X-Pg-Spam-Score: -0.0 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 08/22/2013 06:37 PM, Tom Lane wrote: > A > Do we have a reliable way of generating a unique identifier for each slave > (independently of how that might be exposed)? Probably we could just generate an unique UUID when we first detect that we are replicating from the master with same UUID. This of course requires this master UUID to be present in some way in the replication stream Cheers -- Hannu Krosing PostgreSQL Consultant Performance, Scalability and High Availability 2ndQuadrant Nordic OÜ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers