From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | asti1987 <asti1987(at)gmail(dot)com> |
Subject: | Re: Warning: database postgres must be vacuumed within 1000000 transactions |
Date: | 2011-01-04 15:15:44 |
Message-ID: | 201101040715.45123.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tuesday 04 January 2011 4:06:48 am asti1987 wrote:
> I got a big problem:
> Warning: database 'postgres' must be vacuumed within 1000000 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> Warning: database 'postgres' must be vacuumed within 999999 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> Warning: database 'postgres' must be vacuumed within 999998 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> Warning: database 'postgres' must be vacuumed within 999997 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> backend> vacuum
>
>
> Warning: database 'postgres' must be vacuumed within 999996 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> Warning: database 'postgres' must be vacuumed within 999995 transactions
> HINT: To avoid database shutdown, execute a full database vacuum in
> 'postgres'
>
> its so slow!, i dont know what else to do, it will take 20 days to do it
> all, and i cant wait,
> help me please!
>
What is slow, the vacuum? Are you doing the vacuum on the 'postgres' database?
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | tv | 2011-01-04 15:38:47 | Re: Warning: database postgres must be vacuumed within 1000000 transactions |
Previous Message | Adrian Klaver | 2011-01-04 15:13:21 | Re: What is pg_toast_temp_* in my DB? |