X-Original-To: pgsql-performance@postgresql.org Received: from nycsmtp1out.rdc-nyc.rr.com (nycsmtp1out.rdc-nyc.rr.com [24.29.99.222]) by postgresql.org (Postfix) with ESMTP id 9B5014762B8 for ; Wed, 5 Mar 2003 15:26:46 -0500 (EST) Received: from ibmlaptop (24-29-154-100.nyc.rr.com [24.29.154.100]) by nycsmtp1out.rdc-nyc.rr.com (8.12.1/Road Runner SMTP Server 1.0) with SMTP id h25KQlk5007516 for ; Wed, 5 Mar 2003 15:26:47 -0500 (EST) From: "Tim Mohler" To: Subject: Batch copying of databases Date: Wed, 5 Mar 2003 15:26:27 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal X-Archive-Number: 200303/35 X-Sequence-Number: 1333 Hi all, I'm new to Postgres, and am not even the DBA for the system. I'm just a sysadmin trying to make things run faster. Every month, we copy over a 25 million row table from the production server to the reporting server. Total size is something like 40 gigabytes. The copy in takes close to 24 hours, and I see the disks being hammered by hundreds of small writes every second. The system is mostly waiting on I/O. Is there any facility in Postgres to force batching of the I/O transactions to something more reasonable than 8K? Thanks for any advice, Tim