Re: Kudos on the 64 bit PostgreSQL for Windows

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Dann Corbit <DCorbit(at)connx(dot)com>
Cc: "'Joshua J(dot) Kugler'" <joshua(at)eeinternet(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Kudos on the 64 bit PostgreSQL for Windows
Date: 2010-10-02 02:04:44
Message-ID: 4CA6933C.2060401@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/10/2010 9:41 AM, Dann Corbit wrote:

> The inserts are processed via an INSERT/SELECT statement.
> A custom driver has been written that performs this operation
> using the COPY API.

Aaah, so it's not really sending individual INSERT statements to the
database at all, you're using COPY behind the scenes. That actually
means that all your rows are inserted in one transaction after all.

> I get many thousands of rows per second.

Yep. A COPY happens inside one transaction.

>> Are you using synchronous_commit=off and/or a commit delay?
>
> I do not use synchronous_commit=off
>
>> Do you have fsync=off set in your postgresql.conf?
>
> No.

Good!

Given the performance you were reporting, I thought I'd check. Your use
of COPY explains it, though, because you're actually doing all the work
inside one transaction so the database doesn't have to wait for the disk
after each row insert.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-10-02 07:26:46 Re: Kudos on the 64 bit PostgreSQL for Windows
Previous Message Dann Corbit 2010-10-02 01:41:02 Re: Kudos on the 64 bit PostgreSQL for Windows