Skip site navigation (1) Skip section navigation (2)

Re: Removing postgres -f command line option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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-22 02:24:38
Message-ID: 29618.1321928678@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-11-22 02:32:44
Subject: Re: [COMMITTERS] pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Previous:From: Tom LaneDate: 2011-11-22 02:14:58
Subject: Re: btvacuumpage useless "orig_blkno"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group