From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Borodin Vladimir <root(at)simply(dot)name> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Checksums and full_page_writes |
Date: | 2014-12-26 21:08:31 |
Message-ID: | 20141226210831.GA20689@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Dec 26, 2014 at 04:07:11PM -0500, Bruce Momjian wrote:
> On Fri, Dec 26, 2014 at 01:11:57PM +0300, Borodin Vladimir wrote:
> > Hi all.
> >
> > I ve read thread [0], src/backend/storage/page/README and everything I found in
> > the documentation about checksums [1, 2] but I haven t understood what is my
> > risk if I enable checksums during initdb and turn off full_page_writes?
> >
> > Am I right that I can get torn pages on disk in that case but I will somehow
> > know about it during checksum checking when this page will be read from disk to
> > shared buffers? And is there any way to recover such torn page (from replica or
>
> Yes.
>
> > backup+archived logs, for example)?
>
> There is no way to _fix_ the torn page, but you can ignore the error
> with ignore_checksum_failure:
>
> http://www.postgresql.org/docs/9.4/static/runtime-config-developer.html
Oh, you can fail-over to the replica, of course, but there is no clean
way to restore just the torn page.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Cory Zue | 2014-12-26 22:15:28 | Re: help troubleshooting invalid page header error |
Previous Message | Bruce Momjian | 2014-12-26 21:07:11 | Re: Checksums and full_page_writes |