Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id B2F782E0032 for ; Sat, 26 Apr 2008 10:25:26 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 51488-05 for ; Sat, 26 Apr 2008 10:25:15 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by developer.postgresql.org (Postfix) with ESMTP id ED0C02E002F for ; Sat, 26 Apr 2008 10:25:23 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so2643600rvf.43 for ; Sat, 26 Apr 2008 06:25:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=lc3cRr+MaU2L0kDMOWwbOOKrIL9Hpsc+sYvwRMlQt6A=; b=hXsptfHS9qLGZWvliWY1JrNGIDOBdgVhSI+30P+2GnjwFWEAa5nuMyX2lLf+OoCUa8Kgs9WBsEkr3B/3V+y/0t+IyXSW0yAxxF9QsAqm8semFvGnNb4lFCveM1NFIu8Eor4j4LyBUv3fbZzIdxjsGmKZkcp+lH2zDcHkOBZY55M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=a+l4cmxWpyc9WCly7kzkaQlhNDW4OzdS5MRP4lrN8Lfds/68d47U2hZQNTHm94Z10l1+wgjALIodQFkcO1ImjLsnQUjCqwWn+cRGs6/MUkxR2liEfKkwmhH4JdedFJf90MpgiBA0rKljdEeU7YG7fJiP3Glzf2tQKc7YHaRdhzc= Received: by 10.141.136.19 with SMTP id o19mr2373183rvn.250.1209216322655; Sat, 26 Apr 2008 06:25:22 -0700 (PDT) Received: by 10.141.179.19 with HTTP; Sat, 26 Apr 2008 06:25:22 -0700 (PDT) Message-ID: <8a5d3c890804260625o7ad0700fp79f951c58c242720@mail.gmail.com> Date: Sat, 26 Apr 2008 10:25:22 -0300 From: "Adonias Malosso" To: pgsql-performance@postgresql.org Subject: Best practice to load a huge table from ORACLE to PG MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_697_29964152.1209216322651" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/370 X-Sequence-Number: 29863 ------=_Part_697_29964152.1209216322651 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi All, I=B4d like to know what=B4s the best practice to LOAD a 70 milion rows, 101 columns table from ORACLE to PGSQL. The current approach is to dump the data in CSV and than COPY it to Postgresql. Anyone has a better idea. Regards Adonias Malosso ------=_Part_697_29964152.1209216322651 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi All,

I=B4d like to know what=B4s the best practice to LOAD a 70 m= ilion rows, 101 columns table
from ORACLE to PGSQL.

The current= approach is to dump the data in CSV and than COPY it to Postgresql.
Anyone has a better idea.


Regards
Adonias Malosso
------=_Part_697_29964152.1209216322651--