COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)

From: Mischa <mischa(dot)Sandberg(at)telus(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)
Date: 2005-04-06 18:46:39
Message-ID: 1112813199.42542e8f17b4d@webmail.telus.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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."

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rod Taylor 2005-04-06 19:01:52 Re: Réf
Previous Message Alex Turner 2005-04-06 18:40:29 Re: Réf