Re: Installation instructions vs binaries

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Installation instructions vs binaries
Date: 2020-09-08 14:33:42
Message-ID: CABUevExmd=F5unAqVH55yNo=eJ0dmc1_YcUrdT28XyMAtDDRUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Sep 8, 2020 at 4:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > And I think Davids comment about repetitive language would apply to yours
> > as well, and should maybe be simplified there too?
>
> Per the discussion in the other thread, we concluded that being repetitive
> was the only way to be sure people would see the material at all.
> If you look at
>
> https://www.postgresql.org/docs/devel/runtime.html
>
> a lot of people are going to follow one of the section links before
> they ever see any of the chapter head material.
>

I think we're talking about a different repetitiveness. If I apply Davids
suggestion to that patch, then instead of:

+ <para>
+ If you are using a pre-packaged version
+ of <productname>PostgreSQL</productname>, it may well have a specific
+ convention for where to place the data directory, and it may also
+ provide a script for creating the data directory. In that case you

It would say something like
Pre-packaged versions of PostgreSQL may have a specific convention....

(rest unchanged).

//Magnus

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2020-09-08 14:50:59 Re: Installation instructions vs binaries
Previous Message Tom Lane 2020-09-08 14:27:33 Re: Installation instructions vs binaries