Re: PG backup check
От
Magnus Hagander
Тема
Re: PG backup check
Дата
Msg-id
CABUevEwTU+OECev4=XBoVmq+=oeN5hwzd9JRAD6SndTrPkLhyw@mail.gmail.com
Ответ на
Re: PG backup check (Guillaume Lelarge)
Список
Дерево обсуждения
PG backup check Ravi Krishna <sravikrishna3@gmail.com>
Re: PG backup check Guillaume Lelarge <guillaume@lelarge.info>
Re: PG backup check Magnus Hagander <magnus@hagander.net>
Re: PG backup check Vick Khera <vivek@khera.org>
On Tue, Jul 17, 2018 at 11:17 AM, Guillaume Lelarge <guillaume@lelarge.info> wrote:
2018-07-17 2:35 GMT+02:00 Ravi Krishna <sravikrishna3@gmail.com>:Not sure I am following this. Did Google release this because PG backups are not 100% reliable or the data corruption can occur due to hardware failure.From what I understand with this Google tool, it has nothing to do with backups. It just allows you to check data blocks in a PostgreSQL cluster. Google advice is to run it before taking a backup, but that's about it.
This appears to basically be the same tool that's already included in PostgreSQL 11, and has been around in a few different incarnations (but unpolished) for years.
FWIW, in relation to backups, tools like pgbackrest already did this transparently during backup, and again PostgreSQL 11 will do it built-in.
It's quite possible Google was running this internally before of course, and a separate tool from others, but it's not exactly news... But they do outline a very definite problem, which is that if you get physical corruption in your database, it gets included in the backups. And if it's in a portion of the database you don't use a lot, checksum failures won't be noticed until you actually try, which is way too late.
В списке pgsql-general по дате отправления
