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 1hFIpe-00036z-60 for pgsql-hackers@arkaria.postgresql.org; Sat, 13 Apr 2019 13:36:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hFIpb-0004XL-CY for pgsql-hackers@arkaria.postgresql.org; Sat, 13 Apr 2019 13:36:31 +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 1hFIpa-0004Nc-PL for pgsql-hackers@lists.postgresql.org; Sat, 13 Apr 2019 13:36:31 +0000 Received: from mail-wr1-x442.google.com ([2a00:1450:4864:20::442]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hFIpT-0006Sc-Eq for pgsql-hackers@lists.postgresql.org; Sat, 13 Apr 2019 13:36:29 +0000 Received: by mail-wr1-x442.google.com with SMTP id r4so15479359wrq.8 for ; Sat, 13 Apr 2019 06:36:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hFQYhHcfi2xN3Qqevl18pvacYSgTezS38DWX/oURdVU=; b=fvWqup+dpWPMDj1genNNgAiTM3CLPNIT4TV2LiC/0IXjdRU6eSvs/9Zp9GcEwZKGoF dufP4vt+TGuokymN64TQjjvwjK5HcS+iP3DdddKYtVqRTWqOQMn8dAntqSNRDLwA5H3r UGOqe6+GgAZ6298fZoSKVsBJKExpljTIO33RBhjOiDcnlQotnsOtGxd1K/GxwqcmFySd JdlJ0p+xS9nSQwUWbsXrxqMLSgBdtlG0Td6gWTvQGMrhiB2JuKUTMO960XSRrtJFYXsP UZtQxtY3l/puu9A4OmQCUZCVRo66O+/wioHe/cB7sJ5MGT0iWb7IL+cQKCVeD5vsqzFG 2U+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hFQYhHcfi2xN3Qqevl18pvacYSgTezS38DWX/oURdVU=; b=t1BK/EKjlnQziFpV0h1A8HNijIO5FkzP+OhDZ9zW937RZpEqlCMNnkvGW3T4ECNCIn C6JblEx2Z6mzMEPQ8x5ngzccTr4WYU75sPYeyFcGwDj6NlGbRjclzy3C0uJMeb+IzwVl cpHLcFDlMKY6iZ6UMuwFuytlXH0i1tIQ8bmn+3znX3nBwHb6U9vZxAl78w4mdGtONl7u XRrUEXDN7YV+Ld7c6ITE9oflr2g86/IA0pUBuf/yWVOe7xHfytTpZzCgrmQcPyhTH2s8 aaNcGLfxBbKsyysktD11DwmoNMHCenBSg8HPqybdcpD2NVgXUJnTUEN4DgD3h0q8CyfE TU+g== X-Gm-Message-State: APjAAAXmfB/ewy/n+ktANDAPG0uNc1E/eYq5ippaUoI1L0lLIV21C+d+ UCQwWS3NZsf7qklP6KLe6aZ82g== X-Google-Smtp-Source: APXvYqwjZZe7obahbyLxDnpLfz2Ijicbs+xlOBha+kMKxzFIDr/HHQrYhgfR4vjVYTYTQJ5LC3OAdg== X-Received: by 2002:adf:dc8e:: with SMTP id r14mr16356713wrj.118.1555162581363; Sat, 13 Apr 2019 06:36:21 -0700 (PDT) Received: from localhost (ip-86-49-243-43.net.upcbroadband.cz. [86.49.243.43]) by smtp.gmail.com with ESMTPSA id z14sm65468957wrv.78.2019.04.13.06.36.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 13 Apr 2019 06:36:19 -0700 (PDT) Date: Sat, 13 Apr 2019 15:36:13 +0200 From: Tomas Vondra To: "Fred .Flintstone" Cc: Andreas Karlsson , Chris Travers , Alvaro Herrera , Daniel Gustafsson , Peter Eisentraut , Tatsuo Ishii , Joe Conway , Pavel Stehule , Christoph Berg , Tom Lane , Andres Freund , Mark Kirkwood , Michael Paquier , Euler Taveira , Julien Rouhaud , Postgres hackers Subject: Re: PostgreSQL pollutes the file system Message-ID: <20190413133446.znup73ddhu4o2km2@development> References: <7JPwZOAHfqebBcy9dxAT1zbZ3miMHfUItBVTWx6N4pHPlRgYx0-IO9tthHBRlFKVhKybS8H8ArMHr0AJEF_NfVQHnftQE3fsUgNcegY-Pes=@yesql.se> <20190412132014.GA6802@alvherre.pgsql> <4bc92d6c-982a-a2f6-2caa-68365c184cca@proxel.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-1444-295967 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Please don't top post. It makes it unnecessarily difficult to follow the discussion. See https://wiki.postgresql.org/wiki/Mailing_Lists On Fri, Apr 12, 2019 at 08:56:35PM +0200, Fred .Flintstone wrote: >So there is no regression potential. > I fail to understand how you came to this conclusion? Andreas pointed out Debian already uses pg_createcluster, so there clearly is potential for conflict and a regression. >When and who can send the patch to rename the programs to carry the >pg_ prefixes, and create symlinks from the old names? > Well, presumably that would be you, sometime in the future? TBH I don't quite understand what are we trying to achieve in this thread. It started with the presumption that PostgreSQL "pollutes" the filesystem with scripts/binaries - which may or may not be true, but for the sake of the argument let's assume that it is. How does keeping the original stuff and adding symblinks improve the situation? >On Fri, Apr 12, 2019 at 5:19 PM Andreas Karlsson wrote: >> >> On 4/12/19 5:14 PM, Chris Travers wrote: >> > 1. naming things is surprisingly hard. How sure are we that we can do >> > this right? Can we come up with a correct name for initdb? Maybe >> > pg_createcluster? >> >> The Debian packagers already use pg_createcluster for their script which >> wraps initdb, and while pg_initdb is a bit misleading (it creates a >> cluster rather than a database) it is not that bad. >> >> Andreas regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services