On Thu, 2 Jun 2005 06:19 am, Casey Allen Shobe wrote:
> I found this response to my original post, and tried every single suggestion 
> in it, which has not helped:
> http://archives.postgresql.org/pgsql-performance/2004-11/msg00416.php
> I'm sorry to come begging for help, but this is a MAJOR problem with no 
> logical explanation, and is almost certainly the fault of PostgreSQL, because 
> the database and contents have been identical across all the hosts, and some 
> work beautifully with no tuning whatsoever; so I don't feel I'm wrong in 
> placing blame...

I would personally strongly suggest turing on logging
on the PG server for about an hour, sifting through the runtimes for the 
queries and
finding which ones are taking all the time.  I'd then run explain analyze and 
see what
is happening.  I have heard you could get much better performance by rewriting 
some of
the dspam queries to use PG features.  But I've never used dspam, so I can't 
verify that.

But a quick look through the dspam pg driver source...

    /* Declare Cursor */
    strcpy (query, "DECLARE dscursor CURSOR FOR SELECT DISTINCT username FROM 
    strcpy (query, "DECLARE dscursor CURSOR FOR SELECT DISTINCT uid FROM 

If that's run often, it probably won't give the best performance, but that's a 
Again I'd suggest turning up the logging.

> All machines run Gentoo Linux.  All have the same package versions.  Disk I/O 
> doesn't seem to be related - the 733MHz server had a 33MB/s IDE drive, the 
> 2.4GHz server had a RAID 5 with 3 ultra320 drives:  neither of those required 
> any tuning.  The new 3.0GHz has a mirror raid with 2 ultra320 drives, and the 
> 3000+ that tuning fixed had an ultra160 disk not in a RAID.
> I really like PostgreSQL, and really don't want to use MySQL for dspam, but 
> if 
> I can't get this worked out ASAP I'm going to have to change for the sake of 
> our customers.  Any help is GREATLY appreciated!
Again I'd suggest turning up the logging.

> I'm online on instant messengers (contact IDs shown below), monitoring my 
> email, and will be on #postgresql on Freenode.
> Cheers,

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to