| From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is pg_control file crashsafe? |
| Date: | 2016-05-04 10:10:45 |
| Message-ID: | 5729CAA5.8060706@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On 03.05.2016 2:21, Andres Freund wrote:
> Hi,
>
> On 2016-04-28 21:58:00 +0000, Alex Ignatov wrote:
>> We have some issue with truncated pg_control file on Windows after
>> power failure.My questions is : 1) Is pg_control protected from say ,
>> power crash or partial write?
>
> It should be. I think to make progress on this thread we're going to
> need a bit more details about the exact corruption. Was the length of
> the file change? Did the checksum fail? Did you just observe too old
> contents?
>
> Greetings,
>
> Andres Freund
>
>
Length was 0 bytes after crash. It was Windows and ntfs + ssd in raid 1.
File zeroed after power loss.
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-05-04 10:32:01 | Re: Is pg_control file crashsafe? |
| Previous Message | Craig Ringer | 2016-05-04 10:00:06 | Re: Logical decoding timeline following fails to handle records split across segments |