| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Michael L(dot) Boscia" <mikeboscia(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump after transaction id wraparound failure |
| Date: | 2006-05-15 19:03:07 |
| Message-ID: | 11458.1147719787@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Michael L. Boscia" <mikeboscia(at)gmail(dot)com> writes:
> 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.
Do NOT vacuum. There is zero potential upside and it might delete some
of your data.
It might be worthwhile to try to set the transaction counter back ---
depends on whether you are more worried about losing the oldest data or
newest data. Or you could take two sets of dumps and compare.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-15 19:04:47 | Re: pg_dump after transaction id wraparound failure |
| Previous Message | Martijn van Oosterhout | 2006-05-15 19:01:55 | Re: pg_dump after transaction id wraparound failure |