Re: [PATCH] add long options to pgbench (submission 1)

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] add long options to pgbench (submission 1)
Date: 2013-05-07 09:20:34
Message-ID: alpine.DEB.2.02.1305071111350.10071@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Robert,

>> This very minor patch adds a corresponding long option to all short
>> (one letter) options of pgbench. [...]
>
> I don't really have an opinion on whether this is worth doing, but we'd
> probably want to update all of our client utilities, not just pgbench,
> if we did.

The current status is that "official" clients already have systematic long
options. I have checked: psql, pg_dump, pg_dumpall, pg_restore,
pg_basebackup, createdb, createuser, createlang. Possibly other commands
in contrib do not have long option.

As for the rational, when I type interactively I tend to use short
options, but in a script I like long options so that I may not need to
look them up in the documentation too often when reading the script later.
The other rational is that adding long options is cheap and
straightforward.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-05-07 09:57:14 Fast promotion failure
Previous Message Amit Langote 2013-05-07 09:20:18 XLogFlush invoked about twice as much after 9.2 group commit enhancement