From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-performance@postgresql.org
To: Kevin Grittner <Kgrittn.CCAP.Courts@wicourts.gov>
Subject: Re: Create and drop temp table in 8.3.4
Date: Wed, 05 Nov 2008 17:16:11 -0600
Message-ID: <4911D4DB.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <4911957A.EE98.0025.0@wicourts.gov>
References: <4911957A.EE98.0025.0@wicourts.gov>
>>> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:
> I'm going to get the latest snapshot to see if the issue has changed
> for 8.4devel
In testing under today's snapshot, it seemed to take 150,000 writes to
create and drop 1,000 temporary tables within a database transaction.
The numbers for the various versions might be within the sampling
noise, since the testing involved manual steps and required saturating
the queues in PostgreSQL, the OS, and the RAID controller to get
meaningful numbers. It seems like the complaints of slowness result
primarily from these writes saturating the bandwidth when a query
generates a temporary table in a loop, with the increased impact in
later releases resulting from it getting through the loop faster.
I've started a thread on the hackers' list to discuss a possible
PostgreSQL enhancement to help such workloads. In the meantime, I
think I know which knobs to try turning to mitigate the issue, and
I'll suggest rewrites to some of these queries, to avoid the temporary
tables.
If I find a particular tweak to the background writer or some such is
particularly beneficial, I'll post again.
-Kevin
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: Kevin.Grittner@wicourts.gov, Kgrittn.CCAP.Courts@wicourts.gov
Subject: Re: Create and drop temp table in 8.3.4
In-Reply-To: <4911D4DB.EE98.0025.0@wicourts.gov>
* 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