Remove behaviour of postmaster -o

Andy Chambers wrote:

The first item on the todo list is "remove behaviour
of postmaster -o". Does that simply mean remove the
option and the associated processing from
postmaster.c?

Is anyone working on this?

I've attached a naive patch that does what I've
described above. It compiles and passes the test
script in the tools directory. Is there anything else
this todo should address?

I thought Peter was working on this. Peter?

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Andy Chambers <andychambers2002@yahoo.co.uk> writes:

The first item on the todo list is "remove behaviour
of postmaster -o". Does that simply mean remove the
option and the associated processing from
postmaster.c?

No, it means something closer to this:

http://archives.postgresql.org/pgsql-hackers/2005-12/msg01031.php

http://archives.postgresql.org/pgsql-patches/2006-01/msg00239.php

Not sure why Peter didn't continue working on it.

regards, tom lane

Tom Lane wrote:

http://archives.postgresql.org/pgsql-patches/2006-01/msg00239.php

Not sure why Peter didn't continue working on it.

I'm still working on the postmaster/postgres merge. But the behavior of
postmaster -o is not going to be removed. That TODO item might be
appropriate in a release or three at best.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Peter Eisentraut <peter_e@gmx.net> writes:

Tom Lane wrote:

Not sure why Peter didn't continue working on it.

I'm still working on the postmaster/postgres merge. But the behavior of
postmaster -o is not going to be removed. That TODO item might be
appropriate in a release or three at best.

I think the point though is that -o becomes a no-op: whether you put -o
in front of some options won't matter anymore, because they'll be
interpreted the same either way.

regards, tom lane