Am 01.11.2012 16:10, schrieb Raj Gandhi:
Each DB table has primary key that is populated using DB-sequence.
There is a UNIQUE constraint created on natural keys.
That does sound decent.
The problem on the test setup was because disk cache was enabled.
Indexes were corrupted when powering dow
Re-sending to correct addresses.
>>Seriously, if you're facing DB corruption then something is already
>>horribly wrong with your setup.
>"Horribly" is not strong enough a word IMHO when we're discussing double
primary key values... except if Raj is not using sequences to generate
them. Although
Am 01.11.2012 06:47, schrieb Craig Ringer:
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.
"Horribly" is not strong enough a word IMHO when we're discu
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
