Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCX59-0004EH-41 for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Aug 2013 15:45:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VCX58-0005RK-IB for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Aug 2013 15:45:54 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCX56-0005PP-Gz for pgsql-hackers@postgresql.org; Thu, 22 Aug 2013 15:45:52 +0000 Received: from smtp.01.com ([199.36.142.181] helo=smtp-out-2.01.com) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCX50-0005ja-8R for pgsql-hackers@postgresql.org; Thu, 22 Aug 2013 15:45:51 +0000 Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 6AA2A390365 for ; Thu, 22 Aug 2013 10:45:45 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp-out-2.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlXxI3MVJVj5 for ; Thu, 22 Aug 2013 10:45:45 -0500 (CDT) Received: from smtp-out-2.01.com (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 47EEA39034D for ; Thu, 22 Aug 2013 10:45:45 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 2D61B390365 for ; Thu, 22 Aug 2013 10:45:45 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp-out-2.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sTKnQuyYYHz2 for ; Thu, 22 Aug 2013 10:45:45 -0500 (CDT) Received: from [192.168.42.73] (unknown [206.29.182.245]) by smtp-out-2.01.com (Postfix) with ESMTPSA id C16C739034D for ; Thu, 22 Aug 2013 10:45:44 -0500 (CDT) Message-ID: <52163222.9030700@agliodbs.com> Date: Thu, 22 Aug 2013 08:45:38 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: pg_system_identifier() References: <5215346B.7070800@dalibo.com> <20130822134205.GC17006@awork2.anarazel.de> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.8 (/) 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 All, Vik's feature would be useful for detecting an accidental split in a replication cluster. That is, it would be another tool for detecting if you've made a mistake and created two masters. So +1 from me. It will also be useful for me for sharding. Right now, I'm doing a hackish version of Vik's function, so I'd be glad to have it in core. However, given that the value is the same for all servers in a replication set, are we sure we want to call it system_identifier? Is there a better name? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers