Re: New 'pg' consolidated metacommand patch

From: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: New 'pg' consolidated metacommand patch
Date: 2020-05-27 20:49:12
Message-ID: CAMsGm5cUcQYhOt7W+vz4GFQETQ49zr8j6gnhxuUt=uOZB3tXFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 27 May 2020 at 16:00, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:

> Also consider some practical concerns with the command structure you
> describe: Tab completion of commands wouldn't work anymore, unless you
> supply custom tab completion setups. The direct association between a
> command and its man page would be broken. Shell scripting becomes more
> challenging: Instead of writing common things like "if which
> pg_waldump; then" you'd need some custom code, to be determined. These
> are all solvable, but just a sum of slight annoyances, for no real benefit.
>

I don’t think the man page concern is justified. We could have a “help”
subcommand, just like git; “git help add” is (to a casual observer;
probably not precisely) the same as “man git-add”.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2020-05-27 21:42:18 Re: New 'pg' consolidated metacommand patch
Previous Message Justin Pryzby 2020-05-27 20:30:23 Re: future pg+llvm compilation is broken