pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Adler <adler@pobox.com>
To: John Arbash Meinel <john@arbash-meinel.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: fine tuning for logging server
Date: Thu, 31 Mar 2005 10:01:37 -0500
Message-ID: <20050331150137.GB23069@pobox.com> (raw)
In-Reply-To: <424B6367.8040009@arbash-meinel.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>

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



view thread (10+ messages)

Message-ID: <20050331150137.GB23069@pobox.com>
Permalink:  ../20050331150137.GB23069@pobox.com/
Also on:    postgresql.org/message-id/20050331150137.GB23069@pobox.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: adler@pobox.com, john@arbash-meinel.com
  Subject: Re: fine tuning for logging server
  In-Reply-To: <20050331150137.GB23069@pobox.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox