Re: Glitch in handling of postmaster -o options

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: 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-09-30 15:37:40
Message-ID: 2098.1001864260@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Kreen <marko(at)l-t(dot)ee> writes:
>> I wonder whether we should retire -o.

> How about putting -o stuff after -p? That way only postmaster
> code can set PGC_POSTMASTER options for a backend, no way for
> user to mess up. ATM this would break -o -F tho'.

Indeed. If we're going to force people to change their scripts anyway,
IMHO we might as well go all the way...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2001-09-30 15:40:20 Re: Glitch in handling of postmaster -o options
Previous Message Tom Lane 2001-09-30 15:35:23 Re: PL/pgSQL bug?