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 1iXNEg-0003kk-7B for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2019 10:29:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iXNEe-0002LB-7y for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2019 10:29:20 +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 1iXNEd-0002L3-PG for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2019 10:29:20 +0000 Received: from mail-wr1-x42d.google.com ([2a00:1450:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iXNEa-0007sx-TO for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2019 10:29:18 +0000 Received: by mail-wr1-x42d.google.com with SMTP id s5so27502338wrw.2 for ; Wed, 20 Nov 2019 02:29:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=IBGa5qFoS/0hdHw6X8/bPHjtXPRx8GhYKWUReH1iZ5s=; b=U40j7VXMWJMMzcRLndOvbHvjR4htSC/r0Pa25Gda5p2XeY8yiyedknskzbLfY7UHFc Ydr48PqOTRBOu/MiQ+cu/Pm7cfAqP2gO15/dV9YOjh4EJi57VNRLNBMt//2wFPjEo239 q1/r0rC70NszqGLvLoMsiX6Yw2b2H6b3c37nv5cJc7UzSTJnHFOArA8BE5EFloUUze3F jzDPfu9Ruy7zji4dRGohk3CJbuff3woOm+vLvDJCdorrBSEIXxvejneiJnLFigI4TLqy w2nSn9eA8C1yZRBM/Nthhf9E/VCYBaHVjnyvWEET+RmLLo1IVO6nls/hgj9IAm4bot6C jSBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=IBGa5qFoS/0hdHw6X8/bPHjtXPRx8GhYKWUReH1iZ5s=; b=qytsLf/NSnhMV18f8jRjjZS9TfbNjGLmWuwVP4sXyF0XL4wQNVoHRxvaekm8TTvU9b zIBbkfnXeVneeAZ4XYHySnIPyiCvGf2dWVgsBVZHwWD76bzlMRgBLU5r2fvAXYEfEzIG 7icrm2IMcrGeg3+KQz68hFGMou2wcg2+s0OApwuH/i4bC326cGQWtXNDeKqSLg0NXCBq xjvs+wDW2us//EOgfpUehq2T1/coRplrsELxCsdm81lY708G66EQRDq62P0r3NOVKVsP 9P5VPJjBnZcttmrC4Eqhv0O0tTHzQ6sIKv1Ot7bDDzhBnHKbGfRmY99eXzEpWfvio+Tu 6z/g== X-Gm-Message-State: APjAAAVnM+jpF4G3sZZWSbeNXarEF0qRCo7cq7iTuofIv3brfnwlXg11 TyPPlVZTMd+6qPKfGdbL0DgZcg== X-Google-Smtp-Source: APXvYqypxppihn8IOdDRIIW0qewtcEI6xTUjF0Tr0n5zCK3hwVCsc26xy8JZKR76fx9PAUcvH1pZhA== X-Received: by 2002:adf:f0c4:: with SMTP id x4mr2176895wro.217.1574245754206; Wed, 20 Nov 2019 02:29:14 -0800 (PST) Received: from localhost.localdomain ([212.186.219.234]) by smtp.gmail.com with ESMTPSA id w11sm34842996wra.83.2019.11.20.02.29.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Nov 2019 02:29:13 -0800 (PST) Message-ID: <2dd3a48be2f6b7b18631051b61e568fea98c10ec.camel@cybertec.at> Subject: Re: GSoD - a patch for Getting Started tutorial From: Laurenz Albe To: Tom Lane , Liudmila Mantrova Cc: pgsql-docs@lists.postgresql.org, Stephen Frost , Sarah Conway Schnurr Date: Wed, 20 Nov 2019 11:29:12 +0100 In-Reply-To: <9058.1574179093@sss.pgh.pa.us> References: <54907b90aa20e603eb4204153c7dd5790ce258a4.camel@cybertec.at> <9058.1574179093@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, 2019-11-19 at 10:58 -0500, Tom Lane wrote: > > 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. The confusion was my fault because I didn't follow the tutorial, but the point is valid (others may make similar blunders). I think that the danger of changing paths in the PGDG binaries is limited. It might be a good idea to provide links to the documentation of other popular binary distributions, e.g. for MacOS. We can add a disclaimer that details can differ on these platforms. I kind of like the "troubleshooting" section, but I am unsure where to set the limit. What is there currently doesn't cover all potential causes (e.g., connection via TCP, see Windows), but being exhaustive is probably impossible and not even desirable. On the one hand I can see this section as being helpful for the host of people who are having problems connecting, on the other hand the true beginner might have trouble understanding explanations containing terms like "absolute path" and "Unix-domain sockets". (Side remark: I think the spelling should be "UNIX domain sockets".) I'd be sorry if this effort goes to waste, and there are valuable additions here. I think that the material in this patch is an improvement over the "Installation" section in the current tutorial, but that the other sections ("Architectural Fundamentals", "Creating a Database" and "Accessing a Database") are better in the original. And I like the idea of a "troubleshooting" section. Yours, Laurenz Albe