From: | pratikchirania <pratik(dot)chirania(at)hp(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | pgstat wait timeout |
Date: | 2011-12-15 16:55:48 |
Message-ID: | 1323968148476-5078125.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I am having a scenario where I get consistent warnings in the pglog folder:
2011-12-11 00:00:03 JST WARNING: pgstat wait timeout
2011-12-11 00:00:14 JST WARNING: pgstat wait timeout
2011-12-11 00:00:24 JST WARNING: pgstat wait timeout
2011-12-11 00:00:31 JST WARNING: pgstat wait timeout
2011-12-11 00:00:44 JST WARNING: pgstat wait timeout
2011-12-11 00:00:52 JST WARNING: pgstat wait timeout
2011-12-11 00:01:03 JST WARNING: pgstat wait timeout
2011-12-11 00:01:11 JST WARNING: pgstat wait timeout
.
.
.
This is impacting database performance.
The issue persists even when I use the database minimally.
I have tried fine-tuning the Auto-vacuum parameters:
Change the parameter autovacuum_vacuum_cost_delay to 40ms ::: Issue is
reproduced 4 hours after this change
Change the parameter autovacuum_max_workers to 20 ::: I got the warning
message 2 times at times 17:20:12 and 17:20:20. After this, no warnings for
5 hours. Then I tried:
Change the parameter autovacuum_vacuum_cost_delay to: 60ms, Change the
parameter autovacuum_max_workers to: 10::: I got the warning message 2 times
at times 17:20:12 and 17:20:20. After this, no warnings for 5 hours
Any Ideas?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/pgstat-wait-timeout-tp5078125p5078125.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2011-12-15 17:10:30 | Re: IDLE in transaction introspection |
Previous Message | Tom Lane | 2011-12-15 16:48:47 | Re: Moving more work outside WALInsertLock |