| From: | "Michael L(dot) Boscia" <mikeboscia(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | pg_dump after transaction id wraparound failure |
| Date: | 2006-05-15 18:44:01 |
| Message-ID: | 45caccdc0605151144t5ef60c77ie25ed784586b7051@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello-
I currently have a 1.4 TB database (pg version 7.4.8) that is experiencing
transaction id wraparound. I plan to pg_dump the database and initdb and
reload. I may reload into an 8.1 database at this time.
I am curious how to make sure that I indeed get all the data out of the
tables from a pg_dump. I want to ensure that there would not be anything
"hidden" by the transaction id wraparound failure.
My current plan is selectively dump a portion of the data (most current,
organized in tables by date ex xxx_2006_may) and reload. I plan to vaccuum
each table before dumping. Please warn me if this is not enough. Any
assistance is greatly appreciated.
Mike
--
Mike Boscia
mikeboscia at gmail dot com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-05-15 18:48:54 | Re: pg_dump after transaction id wraparound failure |
| Previous Message | Florian G. Pflug | 2006-05-15 18:04:59 | Re: GUI Interface |