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 1h99Pd-0006Lv-P2 for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:20:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h99Pb-0006cs-At for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:20:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h99Pb-0006ck-1v for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:20:15 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h99PX-0000IA-Sd for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:20:14 +0000 Received: by mail-wm1-x344.google.com with SMTP id f3so212868wmj.4 for ; Wed, 27 Mar 2019 07:20:11 -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:content-transfer-encoding:in-reply-to :user-agent; bh=anssUkN1dfjx+SU+COce2+NJ2IKPLZzQjozJGh5yXwE=; b=m5prW2EcniFFE/nwhxRS0H/o5NV2xmvKoTczVMAykGKSrm8I1edWo/RA4lWAbsOOZk n42od5mYGBoYMnJt0JgmB6p7497yJW0MZIVLbki4bRHIyALnjyqM0RUbrmiWLFi/aB1w kGTcluSH04PuDuhttGTnu9DdWMY+uLchC/MvVTiH2vLJarPLStuFi/7VlH+yLd/ytTlK eRwLSjLVv3+0z7yrYBCfFFTnM4bQUXM8hzAvswDXFbCMPJIBYKlVE5KMNTSj79llHU77 2AuP8JUTu3Pf3VMr7qX5pQtCCG1O/sNr5y/WzNI7nMOheEbpPAANsT+vamqS9vWoWwuN OOfQ== 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:content-transfer-encoding :in-reply-to:user-agent; bh=anssUkN1dfjx+SU+COce2+NJ2IKPLZzQjozJGh5yXwE=; b=f1S1JcjfmFwUZzexGmwzgo3Z6feDwOF1vO+0ENHZVGb68WjevS97JthTn/1QSc1fWc Sn0J2qDw/ufIfmF5eaIfA5q0XDWy7BhvqEhHzQ2hu8r0nQ/KcveqgJ6E8xNOrLq5gnLw n9l9DX2LAT4LzQXt3jkkAKKm8d1puuSAEii9oTSxmSG4g4Hqx2qHXsgPMzKB5PZwGBXU wqRiHfO0/mxRJ2x99EUAdHm79ERB/jsNqZAnw2l3wC9tXrI8WQzD4Le7jYKviAH/FtJ/ tvC/FZ+n9pLmSgltzf9XEf6HUHHuvGXC6THjpalQ6thgnCBOaiggnPOQJ378M4bhNDe/ 9geQ== X-Gm-Message-State: APjAAAVs2DDF3lj3J8TPpyZ1grhJh3Pd5YXAOJrxstA3RQU8DucyrEPU RSKvtc1Fv8vYyMGyVCXdnXDaeQ== X-Google-Smtp-Source: APXvYqzzA5r+wmpyQLiUNWAC1twhYYqDtvx0ygOg6+HtPFusaVcd0eE3b6GalvN71gxMtu04ebxt0w== X-Received: by 2002:a1c:4187:: with SMTP id o129mr8805459wma.57.1553696410534; Wed, 27 Mar 2019 07:20:10 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id a10sm30702168wrs.19.2019.03.27.07.20.06 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 27 Mar 2019 07:20:06 -0700 (PDT) Date: Wed, 27 Mar 2019 15:20:05 +0100 From: Tomas Vondra To: Alvaro Herrera Cc: "Fred .Flintstone" , Mark Kirkwood , Tom Lane , Michael Paquier , Andreas Karlsson , Chris Travers , Tatsuo Ishii , Euler Taveira , Julien Rouhaud , Postgres hackers Subject: Re: PostgreSQL pollutes the file system Message-ID: <20190327142005.GB17983@development> References: <20190327135116.GA17983@development> <20190327140018.GA15038@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190327140018.GA15038@alvherre.pgsql> User-Agent: Mutt/1.11.3 (2019-02-01) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Mar 27, 2019 at 11:00:18AM -0300, Alvaro Herrera wrote: >On 2019-Mar-27, Tomas Vondra wrote: > >> I think the consensus in this thread (and the previous ancient ones) is >> that it's not worth it. It's one thing to introduce new commands with the >> pg_ prefix, and it's a completely different thing to rename existing ones. >> That has inherent costs, and as Tom pointed out the burden would fall on >> people using PostgreSQL (and that's rather undesirable). > >I thought the consensus was to rename them, and install symlinks to the >old names. > I know symlinks were mentioned/proposed, but I don't think there's a clear consensus to do that. I might have missed that part of the discussion. That being said, I'm not strongly opposed to doing that, although I still don't see the need to do that ... regard >-- >Álvaro Herrera https://www.2ndQuadrant.com/ >PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services