I've looked at the issue of assimilating the options of postmaster and
postgres, which has been mentioned now and then over the years. Basically,
we have five conflict cases that need to be resolved by breaking one or the
other, namely:
-N
postmaster: max_connections
postgres: do not end command at newline
-o
postmaster: postgres options
postgres: output file
-p
postmaster: port number
postgres: internal use
-S
postmaster: silent mode
postgres: work_mem
-s
postmaster: use SIGSTOP on backend crash
postgres: statistics
Renaming the postgres side of -N, -o, -p, and -s might not really do any harm,
but the -S option used to be very popular on the postgres command-line via -o
from the postmaster, so I'm afraid that this might break existing start
scripts.
Does anyone have suggestions about resolving these conflicts, or should we
just forget about this issue altogether?
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
