From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Subject: | Re: Standalone backends run StartupXLOG in an incorrect environment |
Date: | 2009-09-22 02:26:35 |
Message-ID: | 200909212226.36215.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 21 September 2009 14:24:07 Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > So if you need to enter standalone mode, you'll have to start
> > postmaster, wait for replay to finish, stop it and restart standalone.
>
> Yeah, that's the case at the moment.
>
> > Would this be a problem when you need standalone mode in an emergency,
> > for example when the database won't start due to Xid wraparound?
>
> If it won't run through StartupXLOG under the postmaster, it's not going
> to do so standalone either.
>
Hmm... istr cases where I couldn't startup regular postgres but could in
stand-alone mode that had system indexes disabled...I could be misremembering
that so that the postmaster would start, I just couldn't connect unless in
stand-alone. In any case this does seem less than ideal, but if there aren't
any better options...
--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-09-22 02:34:42 | Re: Using results from INSERT ... RETURNING |
Previous Message | Bruce Momjian | 2009-09-22 02:07:49 | Re: Hot Standby 0.2.1 |