> ... work for you with code built from the cvs tip? I did an update and
> build tonight and see
A bit more information: an unadorned "-i" fails:
myst$ postmaster -i
postgres: invalid option -- r
Usage:
postgres -boot [-d] [-D datadir] [-F] [-o file] [-x num] dbname
-d debug mode
-D datadir data directory
-F turn off fsync
-o file send debug output to file
-x num internal use
DEBUG: startup process 7172 exited with status 1; aborting startup
But no arguments succeeds:
myst$ postmaster
DEBUG: database system was shut down at 2001-10-19 13:38:20 UTC
DEBUG: checkpoint record is at 0/1191A4
DEBUG: redo record is at 0/1191A4; undo record is at 0/0; shutdown TRUE
DEBUG: next transaction id: 98; next oid: 16557
DEBUG: database system is ready
DEBUG: fast shutdown request
DEBUG: shutting down
DEBUG: database system is shut down
And multiple arguments succeeds (without damaging the other arguments):
myst$ postmaster -i -p 12000
DEBUG: database system was shut down at 2001-10-19 13:39:08 UTC
DEBUG: checkpoint record is at 0/1191E4
DEBUG: redo record is at 0/1191E4; undo record is at 0/0; shutdown TRUE
DEBUG: next transaction id: 98; next oid: 16557
DEBUG: database system is ready
DEBUG: fast shutdown request
DEBUG: shutting down
DEBUG: database system is shut down
I've done a "make clean all install", and did not see this symptom
earlier (I've been building and running quite often the last few days
with updated cvs sources).
- Thomas
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
