From: | Patrik Karlsson <pata(dot)karlsson(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: What should I do after a power loss? |
Date: | 2015-11-07 08:15:51 |
Message-ID: | CANiFHSE5EQPbtx=A69Yqe53SdnXwxwkQHGP5Rz9FZx2K3eEiJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
2015-08-18 21:48 GMT+02:00 Kevin Grittner <kgrittn(at)ymail(dot)com>:
> Patrik Karlsson <pata(dot)karlsson(at)gmail(dot)com> wrote:
>
> > I had a power loss on a Windows 7 machine running PostgreSQL
> > 9.4.4.
>
> As long as you were running with fsync = on and full_page_writes =
> on, and the OS and hardware honor fsync requests, your database
> should not have been corrupted. If you were running with
>
Yes it was, I verified it and it was the default setting I had.
> It sounds unlikely that you will need to go back to the backup, but
> out of paranoia I would keep that particular backup around for a
> few months, in addition to the usual backup rotation.
>
I kept it but I have not felt the need to use it, everything is ok.
>
> > I would like to confirm that everything is ok, how can I do that,
> > (with pgAdmin)?
>
> PostgreSQL is designed to come back from such an event without data
> loss or corruption, and there is no one tool to comprehensively
> look for all forms of inconsistency. You might want to consider
> running pg_catcheck, just to make sure it doesn't find anything
> odd.
>
> https://github.com/EnterpriseDB/pg_catcheck
>
>
I could not get it to work on the windows machine but I'll keep it in mind.
This was a while back and I have now moved the database to a more stable
and monitored environment.
Thanks for your advice.
/Patrik
From | Date | Subject | |
---|---|---|---|
Next Message | Shmagi Kavtaradze | 2015-11-08 16:18:09 | Insert text to column using copy command |
Previous Message | lmanorders | 2015-11-04 18:00:25 | Re: Table Join Problem |