Re: pg_ctl restart - behaviour based on wrong instance - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_ctl restart - behaviour based on wrong instance
Date
Msg-id 201110121810.p9CIAv823177@momjian.us
Whole thread Raw
In response to Re: pg_ctl restart - behaviour based on wrong instance  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_ctl restart - behaviour based on wrong instance  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander wrote:
> > I looked over this issue and I don't thinking having pg_ctl restart fall
> > back to 'start' is a good solution. ?I am concerned about cases where we
> > start a different server without shutting down the old server, for some
> > reason. ?When they say 'restart', I think we have to assume they want a
> > restart.
> >
> > What I did do was to document that not backing up postmaster.pid and
> > postmaster.opts might help prevent pg_ctl from getting confused.
> 
> Should we exclude postmaster.opts from streaming base backups? We
> already exclude postmaster.pid...

Uh, I think so, unless my analysis was wrong.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] *.sql contrib files contain unresolvable MODULE_PATHNAME
Next
From: Magnus Hagander
Date:
Subject: Re: [BUGS] *.sql contrib files contain unresolvable MODULE_PATHNAME