Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: recovery from xid wraparound


  • 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: Tue, 24 Oct 2006 15:28:45 +0100
  • Message-id: <64F50E3BAAE32A4FA0686CF651E0D476146BCC(at)exchange11(dot)ad(dot)edigitalresearch(dot)com>

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




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group