Re: Removing postgres -f command line option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing postgres -f command line option
Date: 2011-11-17 15:56:36
Message-ID: 12532.1321545396@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-11-17 16:03:45 Re: Configuration include directory
Previous Message Peter Geoghegan 2011-11-17 15:44:25 Re: ISN was: Core Extensions relocation