| From: | ramistuni <ramistuni(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Hot Standby performance issue |
| Date: | 2013-10-25 21:22:51 |
| Message-ID: | 1382736171070-5775972.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Today morning I found that the performance issue on standby database was
fixed by itself. On further investigation I found that one of the biggest
used in this query had autovacuum kicked in yesterday on primary. The last
time it had autovaccum ran was on Sep 30th.
I am suspecting that this should have been fixed the issue. The table has
update and delete operations. Only thing I did not understand why postgres
did not pick this table for autovacuum all these days, in spite of this
table is one of the busiest table from DML perspective. I was monitoring the
primary database activity all these days and always could see autovacuum was
running on another tables.
Thanks.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Hot-Standby-performance-issue-tp5774673p5775972.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2013-10-26 14:16:26 | Re: Hot Standby performance issue |
| Previous Message | sparikh | 2013-10-23 01:23:20 | Re: Hot Standby performance issue |