MIME-Version: 1.0
References: <13c65997-9502-7671-1a7b-50e5d5093514@purtz.de>
 <40aca6b45b0da614b94c8ef86d89b70b@xs4all.nl>
 <4b8bdb3b-10a7-e541-18ff-6a556ce89cd1@purtz.de>
 <9df5b9c8-71fe-47a8-4670-346a0ae7e2cd@purtz.de>
 <d2a0cb79-7c87-9bb2-2bb9-9465ba69d854@2ndquadrant.com>
 <f3eeae6c-7e4d-4185-d792-9c97b9fd65f1@purtz.de>
 <567f7c92-dce9-7424-9022-54b31eb12740@purtz.de>
 <1B5F7D1E-B389-4D3B-973A-A8D183D8530A@yesql.se>
 <fdd0fd52-84d3-f7a1-b8c7-aed108d95615@purtz.de>
 <766cab17c6af48956558611520956b77@xs4all.nl>
 <ddfd3e05-407c-5e7b-d9f1-fadee15b5348@purtz.de>
 <d8e2f31f-f2e8-0482-2b10-2ae06a6b8fb7@2ndquadrant.com>
 <93fd8e15-8639-23c8-c7c4-d4cfca323189@purtz.de>
 <CAKFQuwZ_USvnhZ5wQLFtpr8v+iMiwvZOiVZhviQwPYGDVR7w+g@mail.gmail.com>
 <39e77fef-a707-e378-cb13-53ae8d7adb12@purtz.de>
In-Reply-To: <39e77fef-a707-e378-cb13-53ae8d7adb12@purtz.de>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 23 Oct 2020 09:15:14 -0700
Message-ID: 
 <CAKFQuwaOOiSM8oYtkfsCEs-yB4ZH+8H1DgfPKhb-md7yy8Rw2g@mail.gmail.com>
Subject: Re: Additional Chapter for Tutorial
To: =?UTF-8?Q?J=C3=BCrgen_Purtz?= <juergen@purtz.de>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000bd2f6905b258e349"
Precedence: bulk

--000000000000bd2f6905b258e349
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 23, 2020 at 6:58 AM J=C3=BCrgen Purtz <juergen@purtz.de> wrote:

> Creating such a chapter in "VII. Internals" will increase the existing
> chapter numbers 50 - 71, which may lead to some confusion. On the other
> hand the content can possibly be applied to all supported PG versions at
> the same time, which will lead to a consistent behavior. Extending one of
> the existing chapters won't work because all of them handle their own
> topic, eg.: "50. Overview of PostgreSQL Internals" (misleading title?)
> focuses on the handling of SQL statements from parsing to execution.
>
> What are your thoughts?
>
v14 has already added a new chapter, installation from binaries.  It was
not back-patched.  To my knowledge no one brought up these points - numbers
changing or back-patching the new material.  I don't see that this
enhancement needs to be treated any differently.

David J.

--000000000000bd2f6905b258e349
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Fri, Oct 23, 2020 at 6:58 AM J=C3=BCrgen Purtz &lt;<a h=
ref=3D"mailto:juergen@purtz.de">juergen@purtz.de</a>&gt; wrote:</span><br><=
/div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div>
    <p>Creating such a chapter in &quot;VII. Internals&quot; will increase =
the
      existing chapter numbers 50 - 71, which may lead to some
      confusion. On the other hand the content can possibly be applied
      to all supported PG versions at the same time, which will lead to
      a consistent behavior. Extending one of the existing chapters
      won&#39;t work because all of them handle their own topic, eg.: &quot=
;50.
      Overview of PostgreSQL Internals&quot; (misleading title?) focuses on
      the handling of SQL statements from parsing to execution. <br>
    </p>
    <p> What are your thoughts?</p></div></blockquote><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif">v14 has already ad=
ded a new chapter, installation from binaries.=C2=A0 It was not back-patche=
d.=C2=A0 To my knowledge no one brought up these points - numbers changing =
or back-patching the new material.=C2=A0 I don&#39;t see that this enhancem=
ent=C2=A0needs to be treated any differently.</div><div class=3D"gmail_defa=
ult" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">David J=
.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif"><br></div></div></div>

--000000000000bd2f6905b258e349--