Re: Recovery inconsistencies, standby much larger than primary - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Recovery inconsistencies, standby much larger than primary
Date
Msg-id 13123.1391233581@sss.pgh.pa.us
Whole thread Raw
In response to Re: Recovery inconsistencies, standby much larger than primary  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> FWIW, we've periodically seen reports from our clients of replica
> databases being slightly larger than the master.  Nothing reproducable
> or as severe as Greg's issue, or we'd have reported it.  But this could
> be a more widespread issue, just that it affects most users in the +5%
> ballpark, so they don't notice.

Well, the "bloat" aspect of it is really the least of our problems.
AFAICT what is happening is flat-out index corruption, that is, an
intended update isn't applied where it should be but to some
seemingly-random other page.  If this is common then it seems like we
ought to be hearing a lot of reports of query misbehavior on slaves.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Retain dynamic shared memory segments for postmaster lifetime
Next
From: Amit Kapila
Date:
Subject: Re: [bug fix] pg_ctl always uses the same event source