Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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. 


In response to

pgsql-performance by date

Next:From: Steve WamplerDate: 2005-03-31 15:48:09
Subject: Re: Reading recommendations
Previous:From: Stefan WeissDate: 2005-03-31 13:57:55
Subject: Re: Reading recommendations

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group