Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id D74BE2E0040 for ; Sat, 26 Apr 2008 12:10:21 -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 79126-04 for ; Sat, 26 Apr 2008 12:10:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id D309F2E0056 for ; Sat, 26 Apr 2008 12:10:18 -0300 (ADT) Received: from [192.168.1.226] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m3QFAxdm015448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Apr 2008 08:10:59 -0700 Message-ID: <481345E0.5050900@commandprompt.com> Date: Sat, 26 Apr 2008 08:10:24 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Adonias Malosso CC: pgsql-performance@postgresql.org Subject: Re: Best practice to load a huge table from ORACLE to PG References: <8a5d3c890804260625o7ad0700fp79f951c58c242720@mail.gmail.com> In-Reply-To: <8a5d3c890804260625o7ad0700fp79f951c58c242720@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Sat, 26 Apr 2008 08:10:59 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/372 X-Sequence-Number: 29865 Adonias Malosso wrote: > Hi All, > > I´d like to know what´s 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. Write a java trigger in Oracle that notes when a row has been added/delete/updated and does the exact same thing in postgresql. Joshua D. Drake > > > Regards > Adonias Malosso