Re: Performance nightmare with dspam (urgent) (resolved)

From: PFC <lists(at)boutiquenumerique(dot)com>
To: "Casey Allen Shobe" <lists(at)seattleserver(dot)com>, "Postgresql Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
Date: 2005-06-06 15:11:31
Message-ID: op.srye5hubth1vuj@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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,

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Stone 2005-06-06 15:19:11 Re: Performance nightmare with dspam (urgent) (resolved)
Previous Message John A Meinel 2005-06-06 15:08:23 Re: Performance nightmare with dspam (urgent) (resolved)