Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 681B96350B3 for ; Mon, 5 Apr 2010 09:10:34 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 02852-02-6 for ; Mon, 5 Apr 2010 12:10:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id A33D4634E25 for ; Mon, 5 Apr 2010 09:09:26 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id o35C9MB10324; Mon, 5 Apr 2010 08:09:22 -0400 (EDT) From: Bruce Momjian Message-Id: <201004051209.o35C9MB10324@momjian.us> Subject: Re: temp table "on commit delete rows": transaction overhead In-Reply-To: To: Artiom Makarov Date: Mon, 5 Apr 2010 08:09:22 -0400 (EDT) CC: Tom Lane , pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201004/34 X-Sequence-Number: 38284 Artiom Makarov wrote: > 2010/4/1 Bruce Momjian : > > > I think one of the problems is that we do the truncate even if the table > > has not be touched by the query, which is poor behavior. > > Thank you for the support. > Will be this problem registered? I have it on my personal TODO and will try to get it on the official TODO soon. > I see a workaround: switch off "on commit delete rows" on temp tables > and use txid_current() to control transaction visibility. OK. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com