pg_ctl wish list

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_ctl wish list
Date: 2001-02-04 22:52:00
Message-ID: Pine.LNX.4.30.0102042336030.864-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

To alleviate the need for a start up script somewhat we could perhaps fix
up pg_ctl to serve that purpose better.

-w should be the default, as has been suggested.

"fast" shutdown should be the default, otherwise you may get surprises on
system shutdown when users are still connected.

There should be an option to put the server log somewhere, either a file
or maybe a pipe, e.g.,

pg_ctl -l logfile
pg_ctl -P 'magic-log-rotator -x -y -z'

The current behaviour, start server in background and leave stdin/stdout
on terminal, and no nohup, is just plain wrong.

I think there should also be a reasonable defense against not using one of
these options, but I'm not sure what that could be. Maybe something like
picking a default file based on PGDATA.

There should be an option to not print informational messages, so startup
scripts can implement their own message systems without resorting to the
draconian '>/dev/null 2>&1'.

Some option that invokes 'su' with an appropriate user name. Not sure
whether you can invoke 'su' portably.

Finally, maybe a default PGDATA would be useful, although I'm not fond of
it personally.

Comments?

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-02-04 23:01:54 Re: Re: [BUGS] syslog logging setup broken?
Previous Message Nic Ferrier 2001-02-04 22:37:12 Re: [HACKERS] Re: syslog logging setup broken?