Re: Glitch in handling of postmaster -o options

Tom Lane wrote:
>
<snip>
>
> I wonder whether we should retire -o. Or change it so that the
> postmaster parses the given options for itself (consequently adjusting
> its copies of GUC variables) instead of passing them on to backends
> for parsing at backend start time.

Retiring -o would seem like a good idea. Just about every person I bump
into that's new to PostgreSQL doesn't get -o right for some time. It's
simple in concept, but different from how every other package works, so
it confuses newcomers who don't know the difference between the
different parts of PostgreSQL.

It would be good if we could just having options that replace each -o
option (i.e. -F instead of -o '-F', -x -y instead of -o '-x -y') so it's
similar to how other programs command line arguments work.

Regards and best wishes,

Justin Clift

>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi