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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: 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:32:47
Message-ID: 27425.1337884367@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> The control file currently is not a very good match because of the current
> requirement of staying below 512 bytes. If we would include the list of
> running xacts that wouldn't be enough.
> I wondered before if there is more to do to fix that then to do the atomic
> write();fsync();rename();fsync(); dance. I don't see a problem with the cost
> of that personally...

The reason for keeping it to one sector is that you're screwed if the
file is broken, so the fewer failure modes the better.

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-05-24 18:38:24 Re: "could not open relation with OID" errors after promoting the standby to master
Previous Message Ian Pye 2012-05-24 18:28:01 Re: Stateful pointers in set-returning functions