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
Hi,
Keaton Adams írta:
> 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:
>
> FATAL: could not remove old lock file "postmaster.pid": Read-only file
> system
> HINT: The file se
Keaton Adams 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
--
Sent via pgsql-general mailing list (pgs
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:
FATAL: could not remove old lock file "postmaster.pid": Read-only file system
HINT: The file seems accidentally left over, but i
