Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1abo7H-0007Zb-Fk for pgsql-docs@arkaria.postgresql.org; Fri, 04 Mar 2016 11:41:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1abo7H-0001m1-2h for pgsql-docs@arkaria.postgresql.org; Fri, 04 Mar 2016 11:41:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1abo7G-0001lt-LC for pgsql-docs@postgresql.org; Fri, 04 Mar 2016 11:41:54 +0000 Received: from mail-wm0-x22b.google.com ([2a00:1450:400c:c09::22b]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1abo7D-0006vL-Ja for pgsql-docs@postgresql.org; Fri, 04 Mar 2016 11:41:53 +0000 Received: by mail-wm0-x22b.google.com with SMTP id p65so26093802wmp.0 for ; Fri, 04 Mar 2016 03:41:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=sHCRKLI+LURvtuAtpK1OYnZFVutdWqnqW7c6TPD2j1Y=; b=0++iWyQomE4QhtrM/GtLGI02uiVka3i3Yof157/tLb7GaWzy/ysDGh8godTIuJR6ak hUZ9VWAtIOA0fZC6eH5G7gPq4plqfWpVi2jKmcUHCWxCo+HyUiJnBAfnzWZgHJ54ETS/ 2pdqdGUlgZIys7mDxkGySHRes7C12EnBnjOWN82o3d3Df1EsKTzu2NILLwIoVHDADDrP ZnKW+XYv8GQ/tfJNRo8Xw3JW55lajLRyEqMOWeEqHPAkWU9isWaUWEo+Ref0GZPr1qSW /grhSxzshTW0dA5iuL0VRgEbMi07rwYlPCdtZ+UuAiSJtUijmsa7mm4I+e0kfp/WEFmk eSpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=sHCRKLI+LURvtuAtpK1OYnZFVutdWqnqW7c6TPD2j1Y=; b=GadyD6sCnLhAerjcqz3T2FDv/1Ic5mwOZJNyvoeguaxxngmuiwVhmR+J9wwNnr/Kxa BvM5uKni1THuCX5dvOG2c2GSQ//6dEJFdImU5FXvaHR4aftsHMayeJ6iA6LDDfRsmBuv q8bEIv6I2qB1G3sNKXEe9Nj7rppufY/A7UvU3rQ5f1W9T/es7wQiDOpaTvaSUXKppt/V 0c0eLSM3Rb/bsARduOz6RmW4mnI/JFV3zARqIIYR5Rz8qjrlSwz8v8gUyE5ED3kOX/u9 lM1BH4DdKQbsSo5ycsggC8Nb3aIcIZxMibTMkgyqYdIuAghx28eyildt6tS0ZyuOewpw Cwgw== X-Gm-Message-State: AD7BkJJCvm1DqqmLqaO1GussBsLEIh8hmzqhie5U5fBTBg2+H/b4jxPclak2wPVSix7A9HvYp3oXhsyTktXCyw== MIME-Version: 1.0 X-Received: by 10.28.156.194 with SMTP id f185mr4448033wme.35.1457091710043; Fri, 04 Mar 2016 03:41:50 -0800 (PST) Received: by 10.195.13.66 with HTTP; Fri, 4 Mar 2016 03:41:49 -0800 (PST) In-Reply-To: <14897.1456930271@sss.pgh.pa.us> References: <14672.1456929392@sss.pgh.pa.us> <14897.1456930271@sss.pgh.pa.us> Date: Fri, 4 Mar 2016 12:41:49 +0100 Message-ID: Subject: Re: Getting Started section From: Magnus Hagander To: Tom Lane Cc: Maciek Sakrejda , pgsql-docs Content-Type: multipart/alternative; boundary=001a114b2e2ec8589a052d3799b4 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --001a114b2e2ec8589a052d3799b4 Content-Type: text/plain; charset=UTF-8 On Wed, Mar 2, 2016 at 3:51 PM, Tom Lane wrote: > Magnus Hagander writes: > > On Wed, Mar 2, 2016 at 9:36 AM, Tom Lane wrote: > >> Agreed, but I should think that properly packaged versions of Postgres > >> will come with some package-specific instructions. Is that missing > >> in Debian's version, or out of date, or did he just not read it? > > > It's definitely there for debian - it's in > > /usr/share/doc/postgresql-common/README.Debian.gz > > > The bigger question is, is it worth actually more or less importing the > > contents of that into our main documentation. > > I'm definitely -1 on that; there are too many distinct packagings and they > change asynchronously to our releases. As a concrete example, the docs > for Red Hat's version needed to change when they moved from SysV init > scripts to systemd boot. Would we want to keep *both* versions of that > in our manual, and explain exactly which RHEL/CentOS/Fedora versions the > different texts applied to? No thanks ... > They have to be maintained *somewhere*. We could also ask the same people, at least for the major platforms, to maintain it as part of our documentation. Doing that would certainly make it easier for *new users*, who are the target of this... If not the whole docs, then we should at least include *exact* instructions for where to find the platform specific docs for big platforms. As in explicitly tell people where the doc files are located on debian, redhat, etc. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ --001a114b2e2ec8589a052d3799b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Mar 2, 2016 at 3:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Haga= nder <magnus@hagander.net>= writes:
> On Wed, Mar 2, 2016 at 9:36 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Agreed, but I should think that properly p= ackaged versions of Postgres
>> will come with some package-specific instructions.=C2=A0 Is that m= issing
>> in Debian's version, or out of date, or did he just not read i= t?

> It's definitely there for debian - it's in
> /usr/share/doc/postgresql-common/README.Debian.gz

> The bigger question is, is it worth actually m= ore or less importing the
> contents of that into our main documentation.

I'm definitely -1 on that; there are too many distinct packaging= s and they
change asynchronously to our releases.=C2=A0 As a concrete example, the doc= s
for Red Hat's version needed to change when they moved from SysV init scripts to systemd boot.=C2=A0 Would we want to keep *both* versions of tha= t
in our manual, and explain exactly which RHEL/CentOS/Fedora versions the different texts applied to?=C2=A0 No thanks ...


They have to be maintained *somewhere*. We could al= so ask the same people, at least for the major platforms, to maintain it as= part of our documentation. Doing that would certainly make it easier for *= new users*, who are the target of this...=C2=A0

If= not the whole docs, then we should at least include *exact* instructions f= or where to find the platform specific docs for big platforms. As in explic= itly tell people where the doc files are located on debian, redhat, etc.

--
=C2=A0Magnus = Hagander
=C2=A0Me: http://www.hagander.net/
=C2=A0Work: http://www.redpill-linpro.com/
--001a114b2e2ec8589a052d3799b4--