Silent data loss in its pure form - Mailing list pgsql-general

From Alex Ignatov
Subject Silent data loss in its pure form
Date
Msg-id c571dfc5-91b0-0df2-4e3f-45bc94c11759@postgrespro.ru
Whole thread Raw
Responses Re: Silent data loss in its pure form  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general

Following this bug reports from redhat https://bugzilla.redhat.com/show_bug.cgi?id=845233

it rising some dangerous issue:

If on any reasons you data file is zeroed after some power loss(it is the most known issue on XFS in the past) when you do
select count(*) from you_table you got zero if you table was in one 1GB(default) file or some other numbers !=count (*) from you_table before power loss
No errors, nothing suspicious in logs. No any checksum errors. Nothing.

Silent data loss is its pure form.

And thanks to all gods that you notice it before backup recycling which contains good data.
Keep in mind it while checking you "backups" in any forms (pg_dump or the more dangerous and short-spoken PITR file backup)

You data is always in danger with "zeroed data file is normal file" paradigm.

-- 
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: Deleting a table file does not raise an error when the table is touched afterwards, why?
Next
From: David W Noon
Date:
Subject: Re: Deleting a table file does not raise an error when the table is touched afterwards, why?