Rural Hunter <ruralhunter@xxxxxxxxx> wrote: > This was changed quite long time ago when I saw too frequent auto > vacuums to prevent the wrap-around on a very busy/large table > which slow down the performance. I will change it back to the > default to see how it works. There was a long-standing bug which could cause over-frequent wraparound prevention autovacuums. As long as you are on the latest minor release, things should be much better now. > I will try the parameters as you suggested too. Possibly. As I said before, I think the symptoms might better fit a situation where the table in need of VACUUM was a shared table and it just happened to mention db1 because that was the database it was scanning at the time. (Every database includes the shared system tables in its catalog.) -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
