From: | Jov <amutu(at)amutu(dot)com> |
---|---|
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 06:11:07 |
Message-ID: | CADyrUxPUG8XQP4v4TwV-Lwkk_u7O0BgXJ_-CJh+awqqtxCtj5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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: http:amutu.com/blog <http://amutu.com/blog>
2013/5/28 Nikhil G Daddikar <ngd(at)celoxis(dot)com>
> 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 production server and I was wondering if there
> there is a way to know when pages get corrupted. 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?
>
> Thanks.
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2013-05-28 06:28:14 | Re: How to check if Postgresql files are OK |
Previous Message | Joshua D. Drake | 2013-05-28 05:23:12 | Re: Most efficient way to initialize a standby server |