From: | Harald Fuchs <use_reply_to(at)protecting(dot)net> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?) |
Date: | 2005-04-07 12:21:53 |
Message-ID: | puwtreg4ke.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
In article <1112813199(dot)42542e8f17b4d(at)webmail(dot)telus(dot)net>,
Mischa <mischa(dot)Sandberg(at)telus(dot)net> writes:
> 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.
Using COPY from DBD::Pg _is_ documented - presumed you use DBD::Pg
version 1.41 released just today.
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Worthington | 2005-04-07 14:17:22 | 4 way JOIN using aliases |
Previous Message | Douglas J. Trainor | 2005-04-07 09:55:59 | Re: How to improve db performance with $7K? |