Re: Glitch in handling of postmaster -o options - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Glitch in handling of postmaster -o options
Date
Msg-id 200109301813.f8UIDYG25572@candle.pha.pa.us
Whole thread Raw
In response to Re: Glitch in handling of postmaster -o options  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Glitch in handling of postmaster -o options  (Marko Kreen <marko@l-t.ee>)
List pgsql-hackers
> Marko Kreen <marko@l-t.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'.

Not sure what you are suggesting here.  Should we keep -o but say all
options after -o are passed to postgres backends:
postmaster -a -b -c -o -f -g -h

In this case, -abc goes to postmaster and -fgh goes to postgres.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Pre-forking backend
Next
From: Bruce Momjian
Date:
Subject: Re: path for contrib/intarray (current CVS)