Re: fine tuning for logging server

From: Michael Adler <adler(at)pobox(dot)com>
To: John Arbash Meinel <john(at)arbash-meinel(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: fine tuning for logging server
Date: 2005-03-31 15:01:37
Message-ID: 20050331150137.GB23069@pobox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Steve Wampler 2005-03-31 15:48:09 Re: Reading recommendations
Previous Message Stefan Weiss 2005-03-31 13:57:55 Re: Reading recommendations