From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | michael(at)linuxmagic(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #903: Performance Hangs during Lookups |
Date: | 2003-02-25 05:44:21 |
Message-ID: | 8115.1046151861@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> We have a postgres backend to our Mail Server product, and encountering
> performance issues. Simple selects are taking 7-10 seconds..
strace is not a particularly useful level of analysis for Postgres
performance problems. I'd suggest looking at your database schema,
the queries you're issuing, and the plans shown by EXPLAIN for those
queries.
I do notice that the bit of trace you've shown us seems to consist of
the startups of two Postgres backend processes. If that's the bulk of
your activity then you need to think about connection pooling. You want
to be issuing more than one useful query per backend launch.
In any case this seems a bit off-topic for pgsql-bugs. I'd suggest
reviewing the pgsql-performance archives, and then posting there if the
solution hasn't become apparent.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2003-02-25 07:03:13 | Re: [BUGS] Date Return must be As per Natural Calander |
Previous Message | Tom Lane | 2003-02-25 04:06:38 | Re: [BUGS] Date Return must be As per Natural Calander |