Tom Lane wrote:

> Fixing this will require rearranging things around InitPostgres
> (in particular, I think InitBufferPoolBackend will have to be
> called directly from postgres.c).  Since that code got rearranged
> quite a bit last month, I'd be hesitant to try to back-patch whatever
> fix we come up with for HEAD.  Seeing that we'd never noticed the
> problem before, I think it's okay to fix it just in HEAD and not
> risk back-patching ... comments?

So if you need to enter standalone mode, you'll have to start
postmaster, wait for replay to finish, stop it and restart standalone.
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?
Frankly I don't have a problem with no backpatching but ...

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

• Standalone backends run StartupXLOG in an incorrect environment at 2009-09-19 17:21:10 from Tom Lane

Responses

• Re: Standalone backends run StartupXLOG in an incorrect environment at 2009-09-21 18:24:07 from Tom Lane

pgsql-hackers by date

Next:	From: Stef Walter	Date: 2009-09-21 18:12:32
	Subject: Re: pg_hba.conf: samehost and samenet [REVIEW]
Previous:	From: Robert Haas	Date: 2009-09-21 18:05:26
	Subject: Re: generic copy options