From: | "Shane Wright" <shane(dot)wright(at)edigitalresearch(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: recovery from xid wraparound |
Date: | 2006-10-24 14:28:45 |
Message-ID: | 64F50E3BAAE32A4FA0686CF651E0D476146BCC@exchange11.ad.edigitalresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom,
Thanks
But are there just 28 (the 28 that have been vacuumed), or are there more (in 7.4).
Happy there's no guarantee, but would help to know any possible damager in my current situation,
Thanks
S
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: 24 October 2006 15:23
To: Shane Wright
Cc: Martijn van Oosterhout; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] recovery from xid wraparound
"Shane Wright" <shane(dot)wright(at)edigitalresearch(dot)com> writes:
>> Just make sure you've really covered *all* the system tables.
> I've been under the impression system tables get done first, then
> user(me)-created tables after -
No, there's no such guarantee. A database-wide vacuum just does the tables in the order it finds 'em in pg_class.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Wright | 2006-10-24 14:47:52 | Re: recovery from xid wraparound |
Previous Message | Tom Lane | 2006-10-24 14:23:19 | Re: recovery from xid wraparound |