X-Original-To: pgsql-performance@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id D60F192584F for ; Wed, 28 May 2003 11:46:06 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 64115-09 for ; Wed, 28 May 2003 11:46:06 -0400 (EDT) Received: from utahisp.com (mail.cyberwires.com [66.239.12.3]) by developer.postgresql.org (Postfix) with ESMTP id 9620892583D for ; Wed, 28 May 2003 11:46:05 -0400 (EDT) Received: from chad [63.230.8.76] by utahisp.com (SMTPD32-8.00) id A9E0BBC02E4; Wed, 28 May 2003 09:46:40 -0600 Message-ID: <027901c32530$273839c0$32021aac@chad> From: "Chad Thompson" To: "pgsql-performance" Subject: >24 hour restore Date: Wed, 28 May 2003 09:12:23 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Declude-Sender: chad@weblinkservices.com [63.230.8.76] X-Declude-Spoolname: Dd9e00bbc02e4ff35.SMD X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam. X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/235 X-Sequence-Number: 2014 I have, what appears to be a big problem. Machine specs AMD 2100+, 1 GIG SDRam, 3 WD HD's 1 - 20 Gig -15 Gig system and 5 Gig Swap mounted as / 2 - 80 Gig (8 M Cache) in Redhat software RAID 1 (mirror) using Adaptec 1200 as an IDE Controller mounted as /usr/local/pgsql Redhat 8 w/ latest kernel and all updates. I have a much slower machine that has been running my database. We are trying to upgrade to the above machine to make things a bit faster. I followed "Tips for upgrading PostgreSQL from 6.5.3 to 7.0.3" by Mark Stosberg with only a few changes [postgres@sqlsrv root]# pg_dump -cs mydbtable >sqlschema.sql [postgres@sqlsrv root]# pg_dump -a mydbtable > sqldump.sql sqlschema.sql = 900K sqldump.sql = 2.4G [sftp files to aforementioned machine] [postgres@newsqlsrv root]# psql -e mydbtable &1 | tee schema-full-results.txt; grep ERROR schema-full-results.txt >schema-err-results.txt All this works perfectly, quite fast but when I ran.... [postgres@newsqlsrv root]# psql -e &1 | tee inserts-full-results.txt; grep ERROR inserts-full-results.txt >inserts-err-results.txt It started off quick, but it got to the first table w/ any real data in it (only about 30k records) and acted like it was frozen. I left it running all night, it finished that table and started on others but it hasnt even gotten to the big tables (2 @ about 9 million records). At this pace it will take several days to finish the restore. I hope this is something easy/stupid that I have missed. I know that w/ mirroring my write times are not improved, but they are DEFINATLY not this bad. I hope that I havent missed any information. Thank you in advance for any direction. Chad