On Thu, Dec 30, 2010 at 12:56 PM, JotaComm <jota(dot)comm(at)gmail(dot)com> wrote:
> Last week I had a serious problem with my PostgreSQL database. My autovacuum
> is OFF, but in September it started to prevent the transaction wraparoud;
> however last week the following message appeared continuously in my log:
> WARNING: database "production" must be vacuumed within 4827083 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> This message appeared for five to six hours; after that, the message
> disappeared from log. Any idea about what could have happened?
I'm thinking that autovacuum kicked into gear to prevent transaction
wraparound. Once it did enough work to stave off disaster, the
warning messages stopped appearing in the log.
> Every day the vacuum is executed on some tables; and on Sundays it's
> executed on all tables. But as the autovacuum is running since September,
> and it runs for a long time, the vacuum was blocked because autovacuum had
> been running on the same table. How should I procede in this case?
I guess the obvious thing to do would be to turn on autovacuum and
forget about manual vacuums.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-12-31 05:34:50|
|Subject: Re: Avoiding rewrite in ALTER TABLE ALTER TYPE|
|Previous:||From: Robert Haas||Date: 2010-12-31 05:07:18|
|Subject: Re: and it's not a bunny rabbit, either|