From: Dimitri Fontaine <dfontaine@hi-media.com>
To: pgsql-performance@postgresql.org
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Adonias Malosso <malosso@gmail.com>
Subject: Re: Best practice to load a huge table from ORACLE to PG
Date: Mon, 28 Apr 2008 09:49:37 +0200
Message-ID: <200804280949.40101.dfontaine@hi-media.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0804270833430.11601@westnet.com>
References: <8a5d3c890804260625o7ad0700fp79f951c58c242720@mail.gmail.com>
<Pine.GSO.4.64.0804270833430.11601@westnet.com>
Hi,
Le dimanche 27 avril 2008, Greg Smith a écrit :
> than SQL*PLUS. Then on the PostgreSQL side, you could run multiple COPY
> sessions importing at once to read this data all back in, because COPY
> will bottleneck at the CPU level before the disks will if you've got
> reasonable storage hardware.
Latest pgloader version has been made to handle this exact case, so if you
want to take this route, please consider pgloader 2.3.0:
http://pgloader.projects.postgresql.org/#_parallel_loadinghttp://pgfoundry.org/projects/pgloader/
Another good reason to consider using pgloader is when the datafile contains
erroneous input lines and you don't want the COPY transaction to abort. Those
error lines will get rejected out by pgloader while the correct ones will get
COPYied in.
Regards,
--
dim
Attachments:
signature.asc (application/pgp-signature, 188B) download
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: dfontaine@hi-media.com, gsmith@gregsmith.com, malosso@gmail.com
Subject: Re: Best practice to load a huge table from ORACLE to PG
In-Reply-To: <200804280949.40101.dfontaine@hi-media.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