* Amit Langote (amitlangot...@gmail.com) wrote:
> How does one validate a backup? Is there any generally practiced way
> of doing that? Or what do you mean when you say "tested" backups?
You restore from it and then query the restored database for expected
contents, at least.
Thanks,
> 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
> fr
there is a wiki page aouble corruption detection：
http://wiki.postgresql.org/index.php?title=Corruption_detection
but I think avoid corruption is more important and practical than try to
check corruption：
http://blog.ringerc.id.au/2012/10/avoiding-postgresql-database-corruption.html
Jov
blog: h
Nikhil,
* Nikhil G Daddikar (n...@celoxis.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
Folks,
I was using PostgreSQL 8.x in development environment when one day I
started getting all kinds of low-level errors while running queries and
eventually had to reinstall. Maybe it was salvageable but since it was a
test database anyway it didn't matter.
We use PostgreSQL 9 on our produ
