Re: Removing postgres -f command line option

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing postgres -f command line option
Date: 2011-11-21 18:27:24
Message-ID: 201111211827.pALIROQ28536@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> > While looking at Shigeru Hanada's foreign join pushdown patch, I noticed
> > a command line option that I didn't know to exist:
>
> > $ postgres --help
> > ...
> > Developer options:
> > -f s|i|n|m|h forbid use of some plan types
>
> Hmm, I thought I'd fixed that help message to match reality recently.
>
> > That seems completely useless to me, because you can also do "-c
> > enable_seqscan=off". Any objections to removing the -f option altogether?
>
> I use it. See also src/test/regress/regressplans.sh, which would become
> greatly less wieldy if it had to spell out the switches long-form.

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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Shulgin 2011-11-21 18:35:16 Notes on implementing URI syntax for libpq
Previous Message Bruce Momjian 2011-11-21 18:12:47 Re: Client library cross-compiling: Win32, Win64, MacOSX. Possible?