Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WwP0i-0000j2-LN for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Jun 2014 04:59:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WwP0h-0004Rk-JW for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Jun 2014 04:59:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WwP0f-0004RO-Qb for pgsql-hackers@postgresql.org; Mon, 16 Jun 2014 04:59:09 +0000 Received: from mout.kundenserver.de ([212.227.17.13]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WwP0b-00079W-Rb for pgsql-hackers@postgresql.org; Mon, 16 Jun 2014 04:59:07 +0000 Received: from ayaki.localdomain (106-69-159-150.dyn.iinet.net.au [106.69.159.150]) by mrelayeu.kundenserver.de (node=mreue105) with ESMTP (Nemesis) id 0LjJqJ-1WJlOo0dzj-00dUZD; Mon, 16 Jun 2014 06:58:53 +0200 Message-ID: <539E7985.5090801@2ndquadrant.com> Date: Mon, 16 Jun 2014 12:58:45 +0800 From: Craig Ringer Organization: 2nd Quadrant User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Heikki Linnakangas , Greg Stark CC: Alvaro Herrera , Andres Freund , Robert Haas , Bruce Momjian , Rajeev rastogi , Ants Aasma , PostgreSQL-development , Markus Wanner Subject: Re: Proposal for CSN based snapshots References: <51B1CB35.4050406@bluegap.ch> <51B6C97B.1070000@bluegap.ch> <5370D323.1070606@vmware.com> <20140512144112.GB9619@awork2.anarazel.de> <5370E267.2020904@vmware.com> <20140515183436.GD25053@momjian.us> <20140515200632.GB16014@awork2.anarazel.de> <20140515213714.GB7857@eldon.alvh.no-ip.org> <53889CCB.7030005@vmware.com> <5388A063.5000209@vmware.com> In-Reply-To: <5388A063.5000209@vmware.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:uq6pkWhhGhaKweAu1SgQqirGkIni5duXQajLXnsz7zj mdYGW6rBP+aczrECEtCx9afV51SPS5v5w63BE2RV+oGqWAY/o4 P/tWt9SLLIib95R+LnM0h4iLQLUDwixpAFz+2Ndz8RPDxXSD4A Z795JEXR0sWR52hUuQM7FfbMESM2YVUTUvnP7y4HKwgAnmq5In 7decWlDyIWxShfruBHn84Fwrfl70WYLn+eVNFqyMPUQg0E+rgJ Lpbc59U1t5XgVQxuJxcTVoZfsMSL46rcKrcBygB0e+kfyjnDck nN8UYfSAjNYRp4J0NNKFaF2fEt7RRUbUz4YUAt5isyLQzwV72y czGdK2nvsHYX450Q46iWQeKafn/3neGoPg4xD0FUt X-Pg-Spam-Score: -1.9 (-) 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 05/30/2014 11:14 PM, Heikki Linnakangas wrote: > > Yeah. To recap, the failure mode is that if the master crashes and > restarts, the transaction becomes visible in the master even though it > was never replicated. Wouldn't another pg_clog bit for the transaction be able to sort that out? -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers