Re: Glitch in handling of postmaster -o options

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Clift <justin(at)postgresql(dot)org>, Marko Kreen <marko(at)l-t(dot)ee>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Glitch in handling of postmaster -o options
Date: 2001-10-12 02:45:02
Message-ID: 200110120245.f9C2j2l09312@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Would someone give me a status on this?
>
> I don't think we need any code changes. If we decide to deprecate -o
> (or anything else), it's just a documentation change. So we can argue
> about it during beta ...
>
> >> If we notify of the impending deprecation now, to actually occur in 7.3,
> >> would we be best intoducing alternative option names somewhere in the
> >> 7.2 beta cycle so people writing scripts for 7.2 can use the new names
> >> and know their scripts will work into the future?
>
> The alternative option names already exist, in the form of GUC
> variables. For example, "--sort-mem=NNN" could replace -S NNN.

I don't think we can remove -o behavior during beta because it will
affect people using -S in startup scripts. I just wanted to know if I
should record this on the TODO list. Added to TODO:

* Remove behavior of postmaster -o after making
postmaster/postgres flags unique

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-10-12 03:25:18 Re: Glitch in handling of postmaster -o options
Previous Message Tatsuo Ishii 2001-10-12 02:22:32 Re: pg_client_encoding