Re: Removing postgres -f command line option - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Removing postgres -f command line option
Date
Msg-id 201111220241.pAM2frS21286@momjian.us
Whole thread Raw
In response to Re: Removing postgres -f command line option  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I think it is hard to argue that such a  user-visible flag is
> > reasonable, even if it helps backend developers avoid some keystrokes.
> 
> > I think flags used only by backend developers should be things that can
> > _only_ be done with flags.
> 
> Huh?  By that argument, we should remove every single postmaster command
> line switch except "-c var=value", because all the other ones are
> shorthands for that --- Peter went to some lengths awhile ago to make
> that true.

I was talking about developer-use-only flags.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Next
From: Mark Kirkwood
Date:
Subject: Rename a database that has connections