From: Artiom Makarov <artiom.makarov@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: temp table "on commit delete rows": transaction overhead
Date: Mon, 5 Apr 2010 11:56:54 +0400
Message-ID: <q2td448ea361004050056ifed022e3t3ca6e2cca7eaac61@mail.gmail.com> (raw)
In-Reply-To: <201004010044.o310iPU08826@momjian.us>
References: <26236.1269971456@sss.pgh.pa.us>
<201004010044.o310iPU08826@momjian.us>
2010/4/1 Bruce Momjian <bruce@momjian.us>:
> 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?
PS
I see a workaround: switch off "on commit delete rows" on temp tables
and use txid_current() to control transaction visibility.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: artiom.makarov@gmail.com, bruce@momjian.us, tgl@sss.pgh.pa.us
Subject: Re: temp table "on commit delete rows": transaction overhead
In-Reply-To: <q2td448ea361004050056ifed022e3t3ca6e2cca7eaac61@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox