| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | Adrian Klaver <aklaver(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org, Robert Shaw <redsmurfau(at)msn(dot)com> |
| Subject: | Re: Vacuum Vs Vacuum Full |
| Date: | 2008-08-05 16:36:48 |
| Message-ID: | 10052.1217954208@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
>> 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".
> 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.
8.2. But you could still get that message, even in CVS HEAD, if
autovacuum was failing to complete for some reason (and had been
failing for quite a long time).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2008-08-05 16:54:36 | Re: Vacuum Vs Vacuum Full |
| Previous Message | Scott Marlowe | 2008-08-05 16:04:14 | Re: replication only |