From: | Milos Babic <milos(dot)babic(at)gmail(dot)com> |
---|---|
To: | Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: recover corrupt DB? |
Date: | 2009-04-23 17:32:59 |
Message-ID: | e0dd88540904231032v254f2d12vcaf268b943b90032@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes.
Some things like duplicate primary key can exist in pg_resetxlog-ed db.
So, dump db and restore it again on clean initialized cluster.
Regards
Milos
On Thu, Apr 23, 2009 at 8:25 PM, Dan Armbrust <
daniel(dot)armbrust(dot)list(at)gmail(dot)com> wrote:
> > In general, pg_resetxlog would be
> > the tool to try here. Don't panic yet. ;-)
> >
> >
>
> Yep, that was the command I was looking for. That at least got the DB
> to a point where it would start, and I was able to do a dump.
>
> So, I dumped and reloaded all of the databases. Things seem fine, but
> bits and pieces of documentation I've seen for pg_resetxlog also
> recommend initdb, and starting over. Is that necessary?
>
> Thanks,
>
> Dan
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | zach cruise | 2009-04-23 17:33:56 | utf8 encoding for template0 and template1? |
Previous Message | Dan Armbrust | 2009-04-23 17:25:42 | Re: recover corrupt DB? |