| From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
|---|---|
| To: | Prabhjot Sheena <prabhjot(dot)sheena(at)rivalwatch(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] WARNING: database must be vacuumed within 8439472 transactions |
| Date: | 2014-07-07 20:15:18 |
| Message-ID: | CABs1bs0vexoRkrPGj7Mor0yFvEp48p_noSSWoV0i5xDn2ORggw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Sounds like you just have to wait until it finishes..
On Mon, Jul 7, 2014 at 12:56 PM, Prabhjot Sheena <
prabhjot(dot)sheena(at)rivalwatch(dot)com> wrote:
> Hello
> We are using postgresql 8.3 database for last 5 yrs for this
> production database and its running fine. This is our critical database
> which runs 24*7. This weekend we started getting these messages
>
> HINT: To avoid a database shutdown, execute a full-database VACUUM.
> WARNING: database must be vacuumed within 8439472 transactions
>
> i am currently running this command
>
> vacuumdb --analyze db
>
> while this command is running i m still getting these messages
>
> WARNING: database must be vacuumed within 2645303 transactions.
>
> The value of number of transactions is going down every minute
>
> Can anyone tell me what is the best way to sort up this issue.
>
> Thanks
> Avi
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Whitney | 2014-07-07 20:22:44 | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |
| Previous Message | Prabhjot Sheena | 2014-07-07 19:56:22 | WARNING: database must be vacuumed within 8439472 transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Whitney | 2014-07-07 20:22:44 | Re: [ADMIN] WARNING: database must be vacuumed within 8439472 transactions |
| Previous Message | Prabhjot Sheena | 2014-07-07 19:56:22 | WARNING: database must be vacuumed within 8439472 transactions |