From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Silent data loss in its pure form |
Date: | 2016-05-30 17:12:17 |
Message-ID: | CAOR=d=0wuxzMePv-rwQd_am6FmoafddPUEsf-QT2J2+A-MBYgQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 30, 2016 at 10:57 AM, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:
> 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.
That bug shows as having been fixed in 2012. Are there any modern,
supported distros that would still have it? It sounds really bad btw.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Westermann | 2016-05-30 17:49:36 | Re: Deleting a table file does not raise an error when the table is touched afterwards, why? |
Previous Message | David W Noon | 2016-05-30 17:02:47 | Re: Deleting a table file does not raise an error when the table is touched afterwards, why? |