Re: New 'pg' consolidated metacommand patch

From: Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
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 15:32:45
Message-ID: 20200527153245.GA40628@elch.exwg.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

## Magnus Hagander (magnus(at)hagander(dot)net):

> Ugh, yeah, please don't do that. Renaming them just to make it "look more
> modern" helps nobody, really. Especially if the suggestion is people should
> be using the shared-launcher binary anyway.

Quick, let's invent a fancy name like "microcommand" for doing this
like we're used to; then we tell people that's the new "modern" (anybody
cares to write a Medium article for that? (why Medium? it's neither
Rare nor Well Done)). What might make sense for (some) version control
systems and is tempting in languages which have forgotten howto shared
library might not be the best architecture for everything. What has
become of the collection of small dedicated tools?

Regards,
Christoph

--
Spare Space

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-05-27 15:56:59 Re: New 'pg' consolidated metacommand patch
Previous Message Dilip Kumar 2020-05-27 14:52:23 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions