I hope someone can urgently help. I was running 8.2.3 with a lot of
pleasure and no-nonsense. Very fast and delightful database that had
me singing paeans.
But I upgraded to 8.2.9 this morning and have had a major slowdown of
the DB processes. How do I begin to test what is going wrong?
I
On 8/28/08, Phoenix Kiula [EMAIL PROTECTED] wrote:
I hope someone can urgently help. I was running 8.2.3 with a lot of
pleasure and no-nonsense. Very fast and delightful database that had
me singing paeans.
But I upgraded to 8.2.9 this morning and have had a major slowdown of
the DB
Phoenix Kiula [EMAIL PROTECTED] schrieb:
I hope someone can urgently help. I was running 8.2.3 with a lot of
pleasure and no-nonsense. Very fast and delightful database that had
me singing paeans.
But I upgraded to 8.2.9 this morning and have had a major slowdown of
the DB processes. How
On 8/28/08, Andreas Kretschmer [EMAIL PROTECTED] wrote:
Please show us a EXPLAIN ANALYSE for this query. Btw, why
random_page_cost=2? (your other post)
The EXPLAIN ANALYZE shows that it's using an INDEX and getting one
row! So I know the SQL is right.
Could it be that the SQL queries become
On Thu, 2008-08-28 at 15:23 +0800, Phoenix Kiula wrote:
But I upgraded to 8.2.9 this morning and have had a major slowdown of
the DB processes. How do I begin to test what is going wrong?
After restart, OS and PostgreSQL caches are cleaned up -- it might also
slow down PostgreSQL a bit.
On Thu, Aug 28, 2008 at 02:44:08PM +0300, Devrim GÜNDÜZ wrote:
After restart, OS and PostgreSQL caches are cleaned up -- it might also
slow down PostgreSQL a bit.
I'll bet this is the right answer -- before, you were mostly getting
things out of cache (memory), and right now everything has to
