X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 193D153AB5 for ; Thu, 31 Mar 2005 16:01:41 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57543-08 for ; Thu, 31 Mar 2005 15:01:40 +0000 (GMT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by svr1.postgresql.org (Postfix) with ESMTP id D716053AEA for ; Thu, 31 Mar 2005 16:01:39 +0100 (BST) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mail1.panix.com (Postfix) with ESMTP id 855D158ABC; Thu, 31 Mar 2005 10:01:42 -0500 (EST) Received: (from adler@localhost) by panix1.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j2VF1gZ12447; Thu, 31 Mar 2005 10:01:42 -0500 (EST) Date: Thu, 31 Mar 2005 10:01:37 -0500 From: Michael Adler To: John Arbash Meinel Cc: pgsql-performance@postgresql.org Subject: Re: fine tuning for logging server Message-ID: <20050331150137.GB23069@pobox.com> References: <1112233809.10313.31.camel@stantz.corp.sgi.com> <1112234574.12159.1.camel@stantz.corp.sgi.com> <424B5C6F.8090609@arbash-meinel.com> <1112236212.12159.28.camel@stantz.corp.sgi.com> <424B6367.8040009@arbash-meinel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <424B6367.8040009@arbash-meinel.com> User-Agent: Mutt/1.4.2.1i X-Hashcash: 1:20:050331:john@arbash-meinel.com::X5kTwSysg0pB70ff:000000000000000 0000000000000000000000003v6E X-Hashcash: 1:20:050331:pgsql-performance@postgresql.org::IY19HS+EB5qwDip5:00000 000000000000000000000000F0Go X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/681 X-Sequence-Number: 11386 On Wed, Mar 30, 2005 at 08:41:43PM -0600, John Arbash Meinel wrote: > If all you are doing is append only logging, the fastest thing is > probably just a flat file. You could have something that comes along > later to move it into the database. It doesn't really sound like you are > using any features a database provides. (normalization, foreign keys, > indexes, etc.) Here's two ideas that I don't think have been mentioned yet: Use copy to bulk load the data instead of individual imports. And if you get desperate, you can run pg with fsync=false since you don't seem to care about re-initializing your whole database in the case of unexpected interruption. -Mike