| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | "Michael L(dot) Boscia" <mikeboscia(at)gmail(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump after transaction id wraparound failure |
| Date: | 2006-05-15 19:11:03 |
| Message-ID: | 1147720263.9755.136.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2006-05-15 at 14:07, Michael L. Boscia wrote:
> On 5/15/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
> > This is one of those rare instances when I'd shut down the server and
> > take a file system backup if I could. However, at 1.4 TB, that might be
> > a bit difficult... :)
>
> What do I do with a filesystem backup after its done? If I copy and
> restore somewhere won't I experience all the same issues?
Well, imagine that things get worse (like that catalog corruption you
mentioned)... If you have a file system backup you can at least get
back to where you are right now. Better to have a huge, useless backup
you don't need laying about than to be thinking 5 minutes after the
vacuum "Man, I wish I had a file system backup..."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | TJ O'Donnell | 2006-05-15 19:24:51 | postgres vs. oracle for very large tables |
| Previous Message | Michael L. Boscia | 2006-05-15 19:07:05 | Re: pg_dump after transaction id wraparound failure |