From: PFC <lists@boutiquenumerique.com>
To: Casey Allen Shobe <lists@seattleserver.com>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
Date: Mon, 06 Jun 2005 17:11:31 +0200
Message-ID: <op.srye5hubth1vuj@localhost> (raw)
In-Reply-To: <200506061454.48018.lists@seattleserver.com>
References: <200506012019.13218.cshobe@seattleserver.com>
<200506061454.48018.lists@seattleserver.com>
> PostgreSQL and say to use MySQL if you want reasonable performance.
If you want MySQL performance and reliability with postgres, simply run
it with fsync deactivated ;)
I'd suggest a controller with battery backed up cache to get rid of the 1
commit = 1 seek boundary.
> Makes it
> real fun to be a DSpam+PostgreSQL user when limits are reached, since
> everyone denies responsibility. Fortunately, PostgreSQL people are
> pretty
> helpful even if they think the client software sucks. :)
>
> Cheers,
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: lists@boutiquenumerique.com, lists@seattleserver.com
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
In-Reply-To: <op.srye5hubth1vuj@localhost>
* 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