From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Nikhil G Daddikar <ngd(at)celoxis(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to check if Postgresql files are OK |
Date: | 2013-05-28 04:56:10 |
Message-ID: | 20130528045610.GZ8597@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Nikhil,
* Nikhil G Daddikar (ngd(at)celoxis(dot)com) wrote:
> We use PostgreSQL 9 on our production server and I was wondering if
> there there is a way to know when pages get corrupted.
It's not great, but there are a few options. First is to use pg_dump
across the entire database and monitor the PG logs to see if it barfs
about anything. Another thing that you can do is to write a script
which pulls out all of the data from each table using an ORDER BY which
matches some index on the table- PG will, generally, use an in-order
index traversal, which will validate the index and the heap, again, to
some extent.
> I see that
> there is some kind of checksum maintained from 9.3 but till then is
> there a way to be notified quickly when such a thing happens? I use
> a basebackup+rsync of WAL files as a disaster recovery solution.
> Will this be useful when such a scenario occurs?
It really depends. Having multiple backups over time will limit the
risk that corruption gets propagated to a slave system. Also, there is
a CRC on the WAL records which are shipped, which helps a bit, but there
are still cases where corruption can get you. The best thing is to have
frequent, tested, backups.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2013-05-28 05:23:12 | Re: Most efficient way to initialize a standby server |
Previous Message | Raghavendra | 2013-05-28 04:51:20 | Re: How to evaluate disk space needed by a table |