X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C87FA9DC82A for ; Mon, 16 Jan 2006 14:10:50 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 04310-04 for ; Mon, 16 Jan 2006 14:10:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 48A7A9DC81F for ; Mon, 16 Jan 2006 14:10:43 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0GIAcaX009998; Mon, 16 Jan 2006 13:10:38 -0500 (EST) To: Alvaro Herrera cc: Alessandro Baretta , pgsql-performance@postgresql.org Subject: Re: Suspending SELECTs In-reply-to: <20060116175738.GB32100@surnet.cl> References: <43CB71AC.20203@barettadeit.com> <9766.1137433907@sss.pgh.pa.us> <20060116175738.GB32100@surnet.cl> Comments: In-reply-to Alvaro Herrera message dated "Mon, 16 Jan 2006 14:57:38 -0300" Date: Mon, 16 Jan 2006 13:10:38 -0500 Message-ID: <9997.1137435038@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.089 required=5 tests=[AWL=0.089] X-Spam-Score: 0.089 X-Spam-Level: X-Archive-Number: 200601/205 X-Sequence-Number: 16683 Alvaro Herrera writes: > I wonder if we could have a way to "suspend" a transaction and restart > it later in another backend. I think we could do something like this > using the 2PC machinery. > Not that I'm up for coding it; just an idea that crossed my mind. It's not impossible, perhaps, but it would require an order-of-magnitude expansion of the 2PC machinery --- the amount of state associated with an open execution plan is daunting. I think there are discussions about this in the archives. regards, tom lane