pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mischa <mischa.Sandberg@telus.net>
To: pgsql-performance@postgresql.org
Subject: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)
Date: Wed,  6 Apr 2005 11:46:39 -0700
Message-ID: <1112813199.42542e8f17b4d@webmail.telus.net> (raw)
In-Reply-To: <33c6269f05040608377dfc9272@mail.gmail.com>
References: <OF9F44D17F.4458ADD0-ONC1256FDB.0027AF25-C1256FDB.002792BB@beauchamp.loxane.fr>
	<33c6269f05040608377dfc9272@mail.gmail.com>

This thread seems to be focusing in on COPY efficiency,
I'd like to ask something I got no answer to, a few months ago.

Using COPY ... FROM STDIN via the Perl DBI (DBD::Pg) interface,
I accidentally strung together several \n-terminated input lines,
and sent them to the server with a single "putline".

To my (happy) surprise, I ended up with exactly that number of rows
in the target table.

Is this a bug? Is this fundamental to the protocol?

Since it hasn't been documented (but then, "endcopy" isn't documented),
I've been shy of investing in perf testing such mass copy calls.
But, if it DOES work, it should be reducing the number of network 
roundtrips.

So. Is it a feechur? Worth stress-testing? Could be VERY cool.

-- 
"Dreams come true, not free."




view thread (6+ messages)  latest in thread

Message-ID: <1112813199.42542e8f17b4d@webmail.telus.net>
Permalink:  ../1112813199.42542e8f17b4d@webmail.telus.net/
Also on:    postgresql.org/message-id/1112813199.42542e8f17b4d@webmail.telus.net

 · 

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: mischa.Sandberg@telus.net
  Subject: Re: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)
  In-Reply-To: <1112813199.42542e8f17b4d@webmail.telus.net>

* 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