| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| 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 13:14:21 |
| Message-ID: | CA+TgmoZXrmTjzRs7CNcGngXu7T5tFeNbuZrh3Bi-8r+8Y8=b=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 17, 2011 at 4:19 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 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
>
> That doesn't include all the options we support, the documentation lists:
> s|i|o|b|t|n|m|h. These are aliases for enable_* planner options, e.g -fs is
> equal to enable_seqscan=off.
>
> That seems completely useless to me, because you can also do "-c
> enable_seqscan=off". Any objections to removing the -f option altogether?
No. Seems useless to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-11-17 13:28:20 | Re: Removing postgres -f command line option |
| Previous Message | Heikki Linnakangas | 2011-11-17 09:19:20 | Removing postgres -f command line option |