Re: "could not open relation with OID" errors after promoting the standby to master

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: "could not open relation with OID" errors after promoting the standby to master
Date: 2012-05-24 18:54:18
Message-ID: 201205242054.18735.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, May 24, 2012 08:46:21 PM Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On Thursday, May 24, 2012 08:32:47 PM Tom Lane wrote:
> >> I'm not sure I believe that we can make a recovery resume from an
> >> arbitrary point in WAL anyway, or that it would be worth the trouble.
> >> Can't we just resume from the last restartpoint?
> >
> > Well, with a decent sized checkpoint_segments getting up2date can take
> > quite a noticeable amount of time...
>
> So? Slow restart is precisely the price you pay for a large checkpoint
> interval.
Well. no. If you stop the master in a orderly fashion it will checkpoint and
thus have a sensible startup time. There is no such possibility for a standby
without interaction with the master.

Andres

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-05-24 19:24:41 Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile
Previous Message Tom Lane 2012-05-24 18:52:05 Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.