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. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
