Re: Corrupted index on 9.0.3 streaming hot standby

From: Jakub Ouhrabka <jakub(dot)ouhrabka(at)comgate(dot)cz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Corrupted index on 9.0.3 streaming hot standby
Date: 2011-03-03 16:39:57
Message-ID: 4D6FC45D.5030709@comgate.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Robert,

> If there hasn't been a system crash on the standby, then it's harder
> to explain. It'd be interesting to compare the disk blocks in the
> index on the standby with the disk blocks in the index on the master
> and figure out which ones are different and in what way. pg_filedump
> might be useful.

I think this is the case. We can even reproduce it: take another backup
of uncorrupted master and the slave is again corrupted.

The strange thing is that this only affects streaming replication
standby, not wal files shipping standby. Maybe we're doing something
wrong...

Could the reason for the strange behaviour (see previous mail) be
something different than corrupted index?

We'll try to reproduce it in testing environment and possibly create
reproducible test case. I'll definitely report back...

Regards,

Kuba

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Josh 2011-03-03 16:41:22 Re: BUG #5911: pg_notify() function only works when channel name is lower case
Previous Message Dave Page 2011-03-03 16:38:40 Re: BUG #5863: help message report 5433 as default port