| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Edson Carlos Ericksson Richter <richter(at)simkorp(dot)com(dot)br>, Martin Marques <martin(dot)marques(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Does PostgreSQL check database integrity at startup? |
| Date: | 2017-12-27 23:03:31 |
| Message-ID: | 0088da88-7249-7292-e922-e0fb6712c535@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/26/17 4:58 PM, Alvaro Herrera wrote:
>
>> pgBackRest will validate all page checksums (including indexes, etc.) in the
>> cluster during backup. Full backups check everything, incr/differential
>> backups check only the files that have changed.
>
> If a table or index file is of zero length when backed up, as in the
> described case, nothing will be checked, right? I mean, there is
> nothing externally indicating that the file ought to be of a different
> size. Am I wrong?
Yes - that is how it works.
> So Edson's situation here would not raise any red
> flags.
It wasn't clear to me from the OP that the primary and standby were
different - I thought there was just a zero file in general.
In any case, my reply was more directed at Pavel's reply about using
pg_dump to validate checksums. There are better ways...
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-12-28 12:16:51 | Re: Does PostgreSQL check database integrity at startup? |
| Previous Message | Alvaro Herrera | 2017-12-27 21:52:04 | Re: Does PostgreSQL check database integrity at startup? |