Skip site navigation (1) Skip section navigation (2)

pg_ctl non-idempotent behavior change

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_ctl non-idempotent behavior change
Date: 2013-04-26 22:09:44
Message-ID: CAMkU=1zKGzGoDoO=u4MON8h6Q=biRL59PTZvRmR9J7uX0yKoyA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
After 87306184580c9c49717, if the postmaster dies without cleaning up (i.e.
power outage), running "pg_ctl start" just gives this message and then
exits:

pg_ctl: another server might be running

Under the old behavior, it would try to start the server anyway, and
succeed, then go through recovery and give you back a functional system.

From reading the archive, I can't really tell if this change in behavior
was intentional.

Anyway it seems like a bad thing to me.  Now the user has a system that
will not start up, and is given no clue that they need to remove
"postmaster.pid" and try again.

The behavior here under the new "-I" flag seems no better in this
situation.  It claims the server is running, when it only "might" be
running (and in fact is not running).

Cheers,

Jeff

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2013-04-26 22:20:50
Subject: Re: Substituting Checksum Algorithm (was: Enabling Checksums)
Previous:From: Jeff DavisDate: 2013-04-26 21:53:10
Subject: Re: Substituting Checksum Algorithm (was: Enabling Checksums)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group