From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Sreekanth Palluru <sree4pg(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Would like to below scenario is possible for getting page/block corruption |
Date: | 2016-12-09 01:44:23 |
Message-ID: | CAB7nPqRadNQX0QiiO8=AKUc7RZR=Z1M-Y4K7NP1AVcPNpB8_6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
(Please top-post that's annoying)
On Fri, Dec 9, 2016 at 10:28 AM, Sreekanth Palluru <sree4pg(at)gmail(dot)com> wrote:
> Can I generalize that, if after step 4) page ( new page or old page) got
> written disk from buffer and crash happens between step 4) and 5) we
> always get
> block corruption issues with Postgres which can only be recovered by setting
> zero_damaged_pages if we just have pg_dump backups and we are OK lose data
> in the affected blocks?
>
> I am also looking at ways of reproducing the issue ? appreciate your advice
> on it ?
Postgres is designed to avoid such corruption problems if
full_page_writes and fsync are enabled, that's a base stone of its
reliability. If you can create a self-contained scenario able to
reproduce a failure, that could be treated as a Postgres bug, but you
are giving no evidence that this is the case.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Sreekanth Palluru | 2016-12-09 03:09:05 | Re: Would like to below scenario is possible for getting page/block corruption |
Previous Message | Sreekanth Palluru | 2016-12-09 01:28:16 | Re: Would like to below scenario is possible for getting page/block corruption |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-12-09 02:31:39 | Re: Importing SQLite database |
Previous Message | Sreekanth Palluru | 2016-12-09 01:28:16 | Re: Would like to below scenario is possible for getting page/block corruption |