Re: Best practice to load a huge table from ORACLE to PG

--nextPart1767675.qCJLfGrkED
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

Le dimanche 27 avril 2008, Greg Smith a =E9crit=A0:
> than SQL*PLUS.  Then on the PostgreSQL side, you could run multiple COPY
> sessions im****ting 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=
=20
want to take this route, please consider pgloader 2.3.0:
  http://pgloader.projects.postgresql.org/#_parallel_loading
  http://pgfoundry.org/projects/pgloader/

Another good reason to consider using pgloader is when the datafile
contain=
s=20
erroneous input lines and you don't want the COPY transaction to abort.
Tho=
se=20
error lines will get rejected out by pgloader while the correct ones will
g=
et=20
COPYied in.

Regards,
=2D-=20
dim

--nextPart1767675.qCJLfGrkED
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIFYGUlBXRlnbh1bkRAlcuAJ9X8NCdCyz61H8LwRR17L/m3vBAmACgrtg9
oxPM0SLlDbJC/cld9F4x7l8=
=qIhZ
-----END PGP SIGNATURE-----

--nextPart1767675.qCJLfGrkED--