From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org, "Qingqing Zhou" <zhouqq@cs.toronto.edu>
Cc: Marc Cousin <mcousin@sigma.fr>
Subject: Re: insert performance for win32
Date: Fri, 04 Nov 2005 10:21:49 -0500
Message-ID: <13733.1131117709@sss.pgh.pa.us> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3417DD7C7@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD7C7@Herge.rcsinc.local>
"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> It doesn't, and it doesn't. :/ Ok, here's where it gets interesting. I
> removed all the newlines from the test output (dump.sql) and got flat
> times ;).
That's bizarre ... I'd have thought a very long line would be more
likely to trigger internal performance problems than the original.
What happens if you read the file with "psql -f dump.sql" instead
of cat/stdin?
BTW, I get flat times for your psql test case on Unix, again both with
local and remote client. So whatever is going on here, it's
Windows-specific.
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, merlin.moncure@rcsonline.com, zhouqq@cs.toronto.edu, mcousin@sigma.fr
Subject: Re: insert performance for win32
In-Reply-To: <13733.1131117709@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