| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Adrian Klaver <aklaver(at)comcast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org, Robert Shaw <redsmurfau(at)msn(dot)com> |
| Subject: | Re: Vacuum Vs Vacuum Full |
| Date: | 2008-08-05 15:21:44 |
| Message-ID: | 48987008.1070208@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver wrote:
> On Monday 04 August 2008 11:04:00 pm Robert Shaw wrote:
>> "WARNING: database "mydb" must be vacuumed within 177009986 transactions
>> HINT: To avoid a database shutdown, execute a full-database VACUUM in
>> "mydb"."Which is reason I ask the question, is full vacuum backup useful
>> for anything other than reclaiming disk space.
>
> Actually its not asking for a VACUUM FULL but a VACUUM of the full database,
> instead of selected tables.
>
> See below for complete details
> http://www.postgresql.org/docs/8.3/interactive/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
BTW, what version of PostgreSQL is this? Database-wide vacuum is no
longer required for XID wraparound issues. I think this was an 8.3
change but might have happened in 8.2, I don't remember.
Matt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Shaw | 2008-08-05 15:23:33 | Re: Vacuum Vs Vacuum Full |
| Previous Message | Tom Lane | 2008-08-05 14:53:53 | Re: FTS on patterns |