Re: pg_ctl restart - behaviour based on wrong instance

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl restart - behaviour based on wrong instance
Date: 2011-10-12 18:10:57
Message-ID: 201110121810.p9CIAv823177@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-10-12 18:21:11 Re: [BUGS] *.sql contrib files contain unresolvable MODULE_PATHNAME
Previous Message Tom Lane 2011-10-12 17:36:27 Re: [BUGS] *.sql contrib files contain unresolvable MODULE_PATHNAME