From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | mark(dot)a(dot)sloan(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_upgrade doc uses inconsistent versions within the doc. |
Date: | 2023-09-26 17:56:27 |
Message-ID: | CAKFQuwZhjKW=wny8h+dh+EtctjAekjfA20qBroZ9Y_1Sbp_u2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Sep 26, 2023 at 10:35 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, Sep 18, 2023 at 08:14:04PM +0000, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/16/pgupgrade.html
> > Description:
> >
> > I feel like for readability the pg_upgrade doc should use the same
> > old_version and new_version examples when showing examples throughout the
> > doc page.
> >
> > as an exmaple I'm looking at :
> > https://www.postgresql.org/docs/current/pgupgrade.html
> >
> > in some places the example commands use v9.6 and v16. (see step 8)
> >
> > but in other places it mixes versions v9.5 and v9.6 (see step 11 sub
> step 8)
>
> Good point. I came up with the attached patch. It uses 9.6 and current
>
I would get rid of any mentions of our old pre-v10 versioning scheme in the
current documentation.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-09-26 20:14:14 | Re: correct documentation in set role |
Previous Message | Bruce Momjian | 2023-09-26 17:34:56 | Re: pg_upgrade doc uses inconsistent versions within the doc. |