pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Petrilli <petrilli@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PFC <lists@boutiquenumerique.com>
Cc: Vivek Khera <vivek@khera.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Impact of checkpoint_segments under continual load conditions
Date: Tue, 19 Jul 2005 14:48:54 -0400
Message-ID: <59d991c40507191148e6f9ec5@mail.gmail.com> (raw)
In-Reply-To: <7843.1121796596@sss.pgh.pa.us>
References: <59d991c4050717100874c08a86@mail.gmail.com>
	<op.st52tvunth1vuj@localhost>
	<59d991c4050719084460b376f1@mail.gmail.com>
	<4541.1121788647@sss.pgh.pa.us>
	<59d991c40507190930244ba9bb@mail.gmail.com>
	<7224.1121791328@sss.pgh.pa.us>
	<59d991c4050719095440cd3de5@mail.gmail.com>
	<7436.1121792725@sss.pgh.pa.us>
	<59d991c405071910133e28031a@mail.gmail.com>
	<7843.1121796596@sss.pgh.pa.us>

On 7/19/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Christopher Petrilli <petrilli@gmail.com> writes:
> >> Are you sure the backend is reading directly from the file, and not
> >> through psql?  (\copy, or COPY FROM STDIN, would go through psql.)
> 
> > The exact command is:
> > COPY test (columnlist...) FROM '/tmp/loadfile';
> 
> I tried to replicate this by putting a ton of COPY commands like that
> into a file and doing "psql -f file ...".  I don't see more than about
> 0.3% CPU going to psql.  So there's something funny about your test
> conditions.  How *exactly* are you invoking psql?

It is a subprocess of a Python process, driven using a pexpect
interchange. I send the COPY command, then wait for the '=#' to come
back.

Chris
-- 
| Christopher Petrilli
| petrilli@gmail.com



view thread (28+ messages)  latest in thread

Message-ID: <59d991c40507191148e6f9ec5@mail.gmail.com>
Permalink:  ../59d991c40507191148e6f9ec5@mail.gmail.com/
Also on:    postgresql.org/message-id/59d991c40507191148e6f9ec5@mail.gmail.com

 · 

reply

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: petrilli@gmail.com, tgl@sss.pgh.pa.us, lists@boutiquenumerique.com, vivek@khera.org
  Subject: Re: Impact of checkpoint_segments under continual load conditions
  In-Reply-To: <59d991c40507191148e6f9ec5@mail.gmail.com>

* 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