Why do we want to %Remove behavior of postmaster -o

Started by Joshua D. Drakeover 19 years ago5 messages
#1Joshua D. Drake
jd@commandprompt.com

Hello,

I was looking at this todo item and I was wondering why we want to do
this? I have had to use -o -P on many occassion and was wondering if
there is something new to replace it in newer PostgreSQL?

Joshua D. Drake
--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

#2Alvaro Herrera
alvherre@commandprompt.com
In reply to: Joshua D. Drake (#1)
Re: Why do we want to %Remove behavior of postmaster -o

Joshua D. Drake wrote:

Hello,

I was looking at this todo item and I was wondering why we want to do
this? I have had to use -o -P on many occassion and was wondering if
there is something new to replace it in newer PostgreSQL?

Uh, are you confusing it with
postgres -O -P?

Keep in mind that postgres (the standalone backend) is not the same as
postmaster, and that the options are case sensitive :-)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Alvaro Herrera (#2)
Re: Why do we want to %Remove behavior of postmaster -o

Alvaro Herrera <alvherre@commandprompt.com> writes:

Joshua D. Drake wrote:

I was looking at this todo item and I was wondering why we want to do
this? I have had to use -o -P on many occassion and was wondering if
there is something new to replace it in newer PostgreSQL?

Keep in mind that postgres (the standalone backend) is not the same as
postmaster, and that the options are case sensitive :-)

Actually, the TODO item is very badly worded. The idea is to get rid of
the spelling differences between postmaster and postgres options, and
then there will be no need for '-o' because you'll just say what you
want --- that is, "-o -foo" and "-foo" will be interchangeable.

Peter posted some preliminary work along this line a couple months ago,
but seems to have gotten stalled by lack of Windows testing.

regards, tom lane

#4Peter Eisentraut
peter_e@gmx.net
In reply to: Tom Lane (#3)
Re: Why do we want to %Remove behavior of postmaster -o

Am Samstag, 3. Juni 2006 04:27 schrieb Tom Lane:

Actually, the TODO item is very badly worded. The idea is to get rid of
the spelling differences between postmaster and postgres options, and
then there will be no need for '-o' because you'll just say what you
want --- that is, "-o -foo" and "-foo" will be interchangeable.

This is already done.

I suppose that the idea was that the -o option should be phased out over a
couple of releases.

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

#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#4)
Re: Why do we want to %Remove behavior of postmaster -o

Peter Eisentraut <peter_e@gmx.net> writes:

Am Samstag, 3. Juni 2006 04:27 schrieb Tom Lane:

Actually, the TODO item is very badly worded. The idea is to get rid of
the spelling differences between postmaster and postgres options, and
then there will be no need for '-o' because you'll just say what you
want --- that is, "-o -foo" and "-foo" will be interchangeable.

This is already done.

Oh, right. The patch you still have uncommitted had to do with getting
rid of the separate postmaster and postgres executables, right? Is that
going anywhere, or did you decide it's not worth the trouble?

regards, tom lane