From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Rural Hunter <ruralhunter(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: wrong database name in error message? |
Date: | 2013-09-16 16:02:52 |
Message-ID: | 1379347372.27022.YahooMailNeo@web162906.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Rural Hunter <ruralhunter(at)gmail(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Natalie Wenz | 2013-09-16 18:34:42 | Dumping a database that is not accepting commands? |
Previous Message | rajkphb | 2013-09-16 04:12:35 | Re: postgresql patching |