Re: Call for objections: deprecate postmaster -o switch? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Call for objections: deprecate postmaster -o switch?
Date
Msg-id 13622.1006802716@sss.pgh.pa.us
Whole thread Raw
In response to Re: Call for objections: deprecate postmaster -o switch?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I just checked and OpenBSD doesn't have the fix either.  Questions:

> 1) should we patch our getopt.c with that single-line fix?

Fixing our getopt seems like a no-brainer: yes.

> 2) should we force our own getopt on FreeBSD and OpenBSD for 7.2?

This is more debatable.  If it were earlier in the beta cycle I'd say
yes, but at this point I don't think we should take any risks for what
is after all a cosmetic issue.  Put it on TODO for 7.3, instead.

> 3) how should we update the docs for this?

"--name=val may not work on some platforms, if not use -c name=val".
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Call for objections: deprecate postmaster -o switch?
Next
From: "Greg Sabino Mullane"
Date:
Subject: cvs/website/make problems