From: Tom Lane <tgl@sss.pgh.pa.us>
To: Artiom Makarov <artiom.makarov@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: temp table "on commit delete rows": transaction overhead
Date: Tue, 30 Mar 2010 13:50:56 -0400
Message-ID: <26236.1269971456@sss.pgh.pa.us> (raw)
In-Reply-To: <d448ea361003300446s3f750d2fj294093419699cb36@mail.gmail.com>
References: <d448ea361003300446s3f750d2fj294093419699cb36@mail.gmail.com>
Artiom Makarov <artiom.makarov@gmail.com> writes:
> When temp tables with "on commit delete rows" exists, I can see a
> strange delay at any begin and commit.
A delay at commit is hardly surprising, because each such temp table
requires filesystem operations at commit (basically an "ftruncate").
I don't recall any operations at transaction start for such tables,
but there may be some.
regards, tom lane
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: tgl@sss.pgh.pa.us, artiom.makarov@gmail.com
Subject: Re: temp table "on commit delete rows": transaction overhead
In-Reply-To: <26236.1269971456@sss.pgh.pa.us>
* 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