Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6YtI-0004L0-Mv for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 10:56:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6YtG-0002pL-V1 for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 10:56:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6YtG-0002pE-Br for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 10:56:10 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6YtC-0001w6-OE for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 10:56:08 +0000 Received: by mail-wm1-x343.google.com with SMTP id o10so18757152wmc.1 for ; Wed, 20 Mar 2019 03:56:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adjust.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YUt7MG75Vv2CQZd4AxX6uryslv+ioIiHOiVzIrGa9Wg=; b=fYDE0OeLY2AZgcf4cufvzzE10WKgbN0zA8SCtBTUyxHoowtwjr1+A5yrsZ3jouv8we zTndgPlRQkAUmyEmYiUiCxZGcSgtV3OirWrFY4wMDZEdRM0RKR6UiVSI0TZGrTnjeum5 /V8Rl8LjMW2+2w4fcMzXjDjWdjxpO6YjLILFLpONvNYtQi6k08/XSFEDYyKwatSGDjRy B+VftSVyP6jNH9yiTie76Rc5Znt7GOfNgDZ/aOt2e6X57eA7svJWhEWqrPCtZCnTWcdQ bX/mJRmuDvM2AFCv3Wc8MsLZXFLeJ6fj4fNzAdBTrr+ZeAIRHRHIbENVWQ/jO2/Ifck2 jHXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YUt7MG75Vv2CQZd4AxX6uryslv+ioIiHOiVzIrGa9Wg=; b=YrV3U7IV1cJvB+QSIdAq+gFMWtXyMXFQSVpUKm/I9zReF66tMapCBVZo54GhyCBCo9 FK+Y+yIwIiUoHnlXHo1AvXV1nUBMOZJTbXuKLOu1+28bn7ZW8WuYrjh+QiHAlPp5Twwp nqrjubB7ttiTL5yScIZMH2hQ0B/pk2G6/7qXLg7/uCz1xjvhLSvu3AQ7NcS+7rN1NFkg 9ln4z7pjL1oQPhhAgAXzykOklsgan8qHwfTm7I0GR/ogv3hpLLTvZjxyBv68+ZsMtZnH dIDICYPrZMWUV//IPJNXw4QbeqfqVLXBkFwZzFETWthQ8DHt6hsj1K0fxQK/fbVSjVQ0 0cCw== X-Gm-Message-State: APjAAAXc8X+R61dR183+khX6VgeASbx7iq0eOadkSWquo4qhKUVgp2QN xoKkAFX0PKsd2pDqfYwp4e/ynE4SnXGYiEZgW1aGGg== X-Google-Smtp-Source: APXvYqxLd0ZFNQUbb16vtagCcQVQSRbYmHrUWbuKGAWbkQr1wPrUflu9QN7klpatDrMHVdyefxxH4s81i+N2jk+iXX0= X-Received: by 2002:a1c:9c12:: with SMTP id f18mr7784775wme.16.1553079364684; Wed, 20 Mar 2019 03:56:04 -0700 (PDT) MIME-Version: 1.0 References: <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> In-Reply-To: <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> From: Chris Travers Date: Wed, 20 Mar 2019 11:55:38 +0100 Message-ID: Subject: Re: PostgreSQL pollutes the file system To: Andreas Karlsson Cc: "Fred .Flintstone" , Postgres hackers Content-Type: multipart/alternative; boundary="000000000000d7211e058484778d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000d7211e058484778d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Mar 20, 2019 at 11:06 AM Andreas Karlsson wrote= : > On 3/19/19 11:19 AM, Fred .Flintstone wrote: > > PostgreSQL pollutes the file system with lots of binaries that it is > > not obvious that they belong to PostgreSQL. > > > > Such as "/usr/bin/createdb", etc. > > > > It would be better if these files were renamed to be prefixed with > > pg_, such as pg_createdb. > > Or even better postgresql-createdb then be reachable by through a > > "postgresql" wrapper script. > > Hi, > > This topic has been discussed before e.g. in 2008 in > https://www.postgresql.org/message-id/47EA5CC0.8040102%40sun.com and > also more recently but I cannot find it in the archives right now. > > I am personally in favor of renaming e.g. createdb to pg_createdb, since > it is not obvious that createdb belongs to PostgreSQL when reading a > script or looking in /usr/bin, but we would need a some kind of > deprecation cycle here or we would suddenly break tons of people's script= s I wouldn't be opposed to this, but I would note two points on a deprecation cycle: 1 Given that people may have tools that work with all supported versions of PostgreSQL, this needs to be a long cycle, and 2. Managing that cycle makes it a little bit of a tough sell. > . > > And as for the git-like solution with a wrapper script, that seems to be > the modern way to do things but would be an even larger breakage and I > am not convinced the advantage would be worth it especially since our > executables are not as closely related and consistent as for example git'= s. > Git commands may be related, but I would actually argue that git commands have a lot of inconsistency because of this structure, See, for example, http://stevelosh.com/blog/2013/04/git-koans/ > > Andreas > > --=20 Best Regards, Chris Travers Head of Database Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com Saarbr=C3=BCcker Stra=C3=9Fe 37a, 10405 Berlin --000000000000d7211e058484778d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Mar 20, 2019= at 11:06 AM Andreas Karlsson <andr= eas@proxel.se> wrote:
On 3/19/19 11:19 AM,= Fred .Flintstone wrote:
> PostgreSQL pollutes the file system with lots of binaries that it is > not obvious that they belong to PostgreSQL.
>
> Such as "/usr/bin/createdb", etc.
>
> It would be better if these files were renamed to be prefixed with
> pg_, such as pg_createdb.
> Or even better postgresql-createdb then be reachable by through a
> "postgresql" wrapper script.

Hi,

This topic has been discussed before e.g. in 2008 in
https://www.postgresql.org/message-i= d/47EA5CC0.8040102%40sun.com and
also more recently but I cannot find it in the archives right now.

I am personally in favor of renaming e.g. createdb to pg_createdb, since it is not obvious that createdb belongs to PostgreSQL when reading a
script or looking in /usr/bin, but we would need a some kind of
deprecation cycle here or we would suddenly break tons of people's scri= pts

I wouldn't be opposed to this, but = I would note two points on a deprecation cycle:
1 =C2=A0Given tha= t people may have tools that work with all supported versions of PostgreSQL= , this needs to be a long cycle, and
2. Managing that cycle makes= it a little bit of a tough sell.=C2=A0
.

And as for the git-like solution with a wrapper script, that seems to be the modern way to do things but would be an even larger breakage and I
am not convinced the advantage would be worth it especially since our
executables are not as closely related and consistent as for example git= 9;s.

Git commands may be related, but I= would actually argue that git commands have a lot of inconsistency because= of this structure,

=C2=A0

Andreas



--
Best Regards,
Chris Travers
Hea= d of Database

Tel= :=C2=A0+49 162 9037 210=C2=A0| Skype: einhverfr |=C2=A0www.adjust.com=C2=A0
<= div style=3D"margin:0cm 0cm 0.0001pt">Saarbr=C3=BCc= ker Stra=C3=9Fe 37a, 10405 Berlin
=
--000000000000d7211e058484778d--