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 1iX5tV-0006mK-Hs for pgsql-docs@arkaria.postgresql.org; Tue, 19 Nov 2019 15:58:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iX5tT-0006JJ-M3 for pgsql-docs@arkaria.postgresql.org; Tue, 19 Nov 2019 15:58:19 +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 1iX5tT-0006JC-B5 for pgsql-docs@lists.postgresql.org; Tue, 19 Nov 2019 15:58:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iX5tQ-0006PK-Tj for pgsql-docs@lists.postgresql.org; Tue, 19 Nov 2019 15:58:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xAJFwETS009059; Tue, 19 Nov 2019 10:58:14 -0500 From: Tom Lane To: Liudmila Mantrova cc: Laurenz Albe , pgsql-docs@lists.postgresql.org, Stephen Frost , Sarah Conway Schnurr Subject: Re: GSoD - a patch for Getting Started tutorial In-reply-to: References: <54907b90aa20e603eb4204153c7dd5790ce258a4.camel@cybertec.at> Comments: In-reply-to Liudmila Mantrova message dated "Tue, 19 Nov 2019 18:22:04 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9057.1574179093.1@sss.pgh.pa.us> Date: Tue, 19 Nov 2019 10:58:13 -0500 Message-ID: <9058.1574179093@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Liudmila Mantrova writes: > On Tue, Nov 19, 2019 at 11:00 AM Laurenz Albe > wrote: >> On Mon, 2019-11-18 at 23:35 +0300, Liudmila Mantrova wrote: >>> I am a bit uncomfortable about having details about the workings of >>> binary packages for specific operating systems in the core >>> documentation. >>> Maybe I'm too sensitive there, but what about having these parts in >>> the Wiki and linking there from the tutorial? >> I also had my doubts about it, but since we are only talking about PGDG >> packages that the community supports, it's probably OK to have it in >> docs? > i'm all for linking to the download page for the exact install commands > (which I did), but i see no harm in mentioning e.g. install/data > directories in documentation. It is something I myself went back to when > working on this tutorial update, so I believe the user will do too. But > let's hope we'll hear other opinions as well before I go and rework it all. Traditionally we've stayed away from this on the grounds that we don't control packaging details and so we wouldn't know when whatever we say becomes obsolete. Moreover, packaging changes tend not to be quantized to happen in sync with Postgres releases, so that even if we know something changed, there'd be a delay to get the word out. Maybe those arguments can be discounted if the proposal is *only* to document the PGDG packages, but will such a restricted solution really satisfy anyone? I'm concerned that novices will not realize that the presented details don't apply to whatever vendor-supplied Postgres they are using. This thread already presents a great example in its confusion over what the default auth method is on Red Hat packages. >> But if we want to cater for clueless beginners, we cannot omit Windows. I have to agree with this point ... fortunately, there's probably only one packaging that's of great interest there, and that's EDB's. regards, tom lane