| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Pasquale" <pasquale(dot)napolitano(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5067: vacuum problem |
| Date: | 2009-09-19 23:33:01 |
| Message-ID: | 11225.1253403181@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Pasquale" <pasquale(dot)napolitano(at)gmail(dot)com> writes:
> I don't connect any more to postres db because postgres needs to vacuum
> operation.
> Then, i use a standalone backend to connect to postgres db.
> Now i'm im in backend> and i write VACUUM FULL.
You don't really need VACUUM FULL, only VACUUM.
> I have this message:
> WARNING: database "postgres" must be vacuumed within 999455 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "postgres".
> 999453
It's not an error, only a warning. You'll get a couple of those for
each table in the VACUUM, but after you finish it should stop complaining.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paulo | 2009-09-20 01:00:03 | BUG #5068: LIKE |
| Previous Message | Tom Lane | 2009-09-19 22:20:25 | Re: notice on explicit primary key or index name |