On 11/01/2012 01:10 PM, Scott Ribe wrote:
> On Oct 31, 2012, at 8:50 PM, Craig Ringer wrote:
>
>> Seriously, if you're facing DB corruption then something is already
>> horribly wrong with your setup.
> True, but. In a past life, complaints from the db (it was a db that stored a
> checksum with ev
On Oct 31, 2012, at 8:50 PM, Craig Ringer wrote:
> Seriously, if you're facing DB corruption then something is already
> horribly wrong with your setup.
True, but. In a past life, complaints from the db (it was a db that stored a
checksum with every block) were the very first symptom when someth
On 11/01/2012 08:01 AM, Raj Gandhi wrote:
>
> I'm looking for ways to detect DB index and any other type of corruption
> in DB. It looks like there is no tool to verify if Postgres DB is
> corrupted or not.
There is no database verifier tool. One would be quite nice to have for
testing and devel
I'm looking for ways to detect DB index and any other type of corruption in
DB. It looks like there is no tool to verify if Postgres DB is corrupted
or not.
I would like to detect some of the following DB corruptions:
- corruption in DB indexes
- detect duplicate primary keys in a table (noti
Hi All,
We are using postgreSQL since 2007 (now we use postgreSQL 8.4) and until
recently we used to perform deletion of old data then vacuum and analyze tasks
by ourself (every night at 0am CET).
Nevertheless we reached a point where these tasks are taking so much time that
why we decide to p
