Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wjt3I-0006uI-67 for pgsql-hackers@arkaria.postgresql.org; Mon, 12 May 2014 16:26:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wjt3H-0002LQ-Le for pgsql-hackers@arkaria.postgresql.org; Mon, 12 May 2014 16:26:07 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wjt3G-0002LI-Hy for pgsql-hackers@postgresql.org; Mon, 12 May 2014 16:26:06 +0000 Received: from mout.kundenserver.de ([212.227.126.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wjt3D-0006K7-HG for pgsql-hackers@postgresql.org; Mon, 12 May 2014 16:26:05 +0000 Received: from anarazel.de (p54AF4393.dip0.t-ipconnect.de [84.175.67.147]) by mrelayeu.kundenserver.de (node=mreue007) with ESMTP (Nemesis) id 0MRvbR-1WLs1Z15kv-00SybG; Mon, 12 May 2014 18:26:00 +0200 Received: by anarazel.de (Postfix, from userid 1000) id 931FF1004EB; Mon, 12 May 2014 18:25:59 +0200 (CEST) Date: Mon, 12 May 2014 18:25:59 +0200 From: Andres Freund To: Heikki Linnakangas Cc: Rajeev rastogi , Ants Aasma , PostgreSQL-development , Markus Wanner Subject: Re: Proposal for CSN based snapshots Message-ID: <20140512162559.GA9535@awork2.anarazel.de> References: <51B1CB35.4050406@bluegap.ch> <51B6C97B.1070000@bluegap.ch> <5370D323.1070606@vmware.com> <20140512144112.GB9619@awork2.anarazel.de> <5370E267.2020904@vmware.com> <20140512152628.GC9619@awork2.anarazel.de> <5370F37F.4060104@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5370F37F.4060104@vmware.com> X-Provags-ID: V02:K0:MQdXMBrhlipLBlmWgVFD3RfJUExFlUUkd1/Y3MVkRI6 3d/v3JsI5j1VFu9UKifacXIImguRGWdCgRWxOv/T4xpbHuqwlI fRzKBrM+oM33nHjLanMoIMrSrOETJXt64rVKl3RPrANG0Hg8Ly 9Wu2tZOZCktdF6VXK1LXvwlFuW5MCMjtcvMXuso+02WjkF6fXT qR8Hf14kuSFZi1BfHAaVJ0mXfF/fS/4qHNF2B311MOh67yCULp 6bhpf6A3tQy1CbjywJuhCDhyctkJw4ca9nHu6DBvL8y2xp6vU+ ert+3U3L2EtZ5ZhQcdOUWo1Mhh/nokEv/MXUoQeq6Y8PDFdKU0 wUvlQqxFYO5Lz1j5Cb3DuctoHUlVjLddBmKL3GpGS 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 2014-05-12 19:14:55 +0300, Heikki Linnakangas wrote: > On 05/12/2014 06:26 PM, Andres Freund wrote: > >>>With the new "commit-in-progress" status in clog, we won't need the > >>>sub-committed clog status anymore. The "commit-in-progress" status will > >>>achieve the same thing. > >Wouldn't that cause many spurious waits? Because commit-in-progress > >needs to be waited on, but a sub-committed xact surely not? > > Ah, no. Even today, a subxid isn't marked as sub-committed, until you commit > the top-level transaction. The sub-commit state is a very transient state > during the commit process, used to make the commit of the sub-transactions > and the top-level transaction appear atomic. The commit-in-progress state > would be a similarly short-lived state. You mark the subxids and the top xid > as commit-in-progress just before the XLogInsert() of the commit record, and > you replace them with the real LSNs right after XLogInsert(). Ah, right. Forgot that detail... Greetings, Andres Freund -- Andres Freund 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