Re: Performance nightmare with dspam (urgent) (resolved) - Mailing list pgsql-performance

From PFC
Subject Re: Performance nightmare with dspam (urgent) (resolved)
Date
Msg-id op.srye5hubth1vuj@localhost
Whole thread Raw
In response to Re: Performance nightmare with dspam (urgent) (resolved)  (Casey Allen Shobe <lists@seattleserver.com>)
List 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,



pgsql-performance by date:

Previous
From: John A Meinel
Date:
Subject: Re: Performance nightmare with dspam (urgent) (resolved)
Next
From: K C Lau
Date:
Subject: Re: SELECT DISTINCT Performance Issue