From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Glaesemann <grzm@seespotcode.net>
Cc: Thomas Finneid <tfinneid@student.matnat.uio.no>
Cc: pgsql-performance@postgresql.org
Subject: Re: insert vs select into performance
Date: Tue, 17 Jul 2007 16:31:20 -0400
Message-ID: <5666.1184704280@sss.pgh.pa.us> (raw)
In-Reply-To: <0D6011B2-D09F-45E8-A5D7-5F84ADD1DC2B@seespotcode.net>
References: <469D1AD3.9030004@ifi.uio.no>
<0D6011B2-D09F-45E8-A5D7-5F84ADD1DC2B@seespotcode.net>
Michael Glaesemann <grzm@seespotcode.net> writes:
> It would be helpful if you included the actual queries you're using,
> as there are a number of variables:
Not to mention which PG version he's testing. Since (I think) 8.1,
SELECT INTO knows that it can substitute one fsync for WAL-logging
the individual row inserts, since if there's a crash the new table
will disappear anyway.
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, grzm@seespotcode.net, tfinneid@student.matnat.uio.no
Subject: Re: insert vs select into performance
In-Reply-To: <5666.1184704280@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