From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Benchmark Data requested |
Date: | 2008-02-06 15:40:20 |
Message-ID: | Pine.GSO.4.64.0802061031440.15780@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, 6 Feb 2008, Dimitri Fontaine wrote:
> Did you compare to COPY or \copy?
COPY. If you're loading a TB, if you're smart it's going onto the server
itself if it all possible and loading directly from there. Would probably
get a closer comparision against psql \copy, but recognize you're always
going to be compared against the best server-side copy method available.
> Do you want to test pgloader again with Marko psycopgwrapper code to see if
> this helps?
Wouldn't have time myself for at least a month (probably not until after
the East convention) so don't go making commits on my behalf.
> Maybe at the end of this PostgreSQL backend code will be smarter than pgloader
> (wrt error handling and data massaging) and we'll be able to drop the
> project
There are way too many data massaging cases I never expect the backend
will handle that pgloader does a great job of right now, and I think there
will always be a niche for a tool like this.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-02-06 15:56:03 | Re: Benchmark Data requested --- pgloader CE design ideas |
Previous Message | Roberts, Jon | 2008-02-06 15:35:47 | Re: Optimizer : query rewrite and execution plan ? |