| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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 00:13:51 |
| Message-ID: | 22912.1002845631@sss.pgh.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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-12 00:26:48 | Re: Deadlock? idle in transaction |
| Previous Message | Tom Lane | 2001-10-12 00:10:38 | Re: CLUSTER TODO item |