From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: postmaster and postgres options assimilation |
Date: | 2005-12-23 19:32:10 |
Message-ID: | 22333.1135366330@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> -S
> postmaster: silent mode
> postgres: work_mem
> 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.
Actually I'd vote for renaming the silent-mode switch. That's pretty
well deprecated anyway isn't it? I've certainly not seen it used in
start scripts.
Similarly, I think it would be less likely to cause problems if you
renamed postmaster -s (SIGSTOP) than postgres -s. I can't imagine
that anyone is using postmaster -s in the field.
> Does anyone have suggestions about resolving these conflicts, or should we
> just forget about this issue altogether?
I don't think we should let the risk of breaking a few start scripts
dissuade us from cleaning up this mess.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-23 20:18:21 | Fixing row comparison semantics |
Previous Message | Peter Eisentraut | 2005-12-23 19:15:47 | postmaster and postgres options assimilation |