I had to calculate out the next transaction ID and -f (force) the change, but
once I did this the DB came back up. So, thanks for the info, and now I know
how this works.
The plan now is to dump the databases and reload them to ensure overall
database integrity.
Thanks for the reply,
Keaton
On 6/8/09 11:46 AM, "Tom Lane" <t...@sss.pgh.pa.us> wrote:
Keaton Adams <kad...@mxlogic.com> writes:
> This is a QA system and unfortunately there is no recent backup.... So as a
> last resort I am looking for any way to bring up Postgres when it has corrupt
> data in it:
pg_resetxlog?
regards, tom lane
