From: | Borodin Vladimir <root(at)simply(dot)name> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Checksums and full_page_writes |
Date: | 2014-12-26 10:11:57 |
Message-ID: | EC425466-3226-48D2-B7BE-D9E223CE91E7@simply.name |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 backup+archived logs, for example)?
[0] http://www.postgresql.org/message-id/20111217213324.GA4497@fetter.org
[1] http://www.postgresql.org/docs/current/static/app-initdb.html#APP-INITDB-DATA-CHECKSUMS
[2] http://www.postgresql.org/docs/current/static/wal-reliability.html
--
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Kumar | 2014-12-26 11:55:08 | Re: help troubleshooting invalid page header error |
Previous Message | Adrian Klaver | 2014-12-25 22:50:58 | Re: Check constraint on foreign table using SQL function |