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 <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1iXSR7-0007wB-KZ
	for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2019 16:02:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1iXSR6-00077i-9f
	for pgsql-docs@arkaria.postgresql.org; Wed, 20 Nov 2019 16:02:32 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <magnus@hagander.net>)
	id 1iXSR5-00077b-UB
	for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2019 16:02:32 +0000
Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <magnus@hagander.net>)
	id 1iXSR3-00057K-5V
	for pgsql-docs@lists.postgresql.org; Wed, 20 Nov 2019 16:02:31 +0000
Received: by mail-lf1-x134.google.com with SMTP id b20so20653489lfp.4
        for <pgsql-docs@lists.postgresql.org>;
 Wed, 20 Nov 2019 08:02:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=hagander-net.20150623.gappssmtp.com; s=20150623;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=AEPLH0/nHvIX2l8ZeBv7pd+8tNHAalZR2wtk9h8Mqqs=;
        b=HeA/lEfGbTW5NuUWFCSs8uNXZaNS9MG6o9UvD4kVvDeIamG4/vrmCE55yX72/GAj5E
         D/OBJFoU+9Qvgy8dulTyYbQVxrhWUrksB959a7cUvlcBftCVKJLpXUekVuGUVeNSsZvA
         Oruj3MWgHQsv25gcwjgMB/dzlC7+KsGzh7jmMBhGKIRlioyT8fJGJYq5Dhgqx+kHhtxZ
         0doA1q0ryTeMSo182fmF5unjoab4JnB/zGEXa0kTagi8VaMMN5LAkj4eifda9ClfH/2M
         gAKLDdUymVsCuF3/Lr1LqxXwaLkgbD1Dqsw9fM8jOs8K5yFTM2ai9vB+i48apxn2tAp2
         1/6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=AEPLH0/nHvIX2l8ZeBv7pd+8tNHAalZR2wtk9h8Mqqs=;
        b=nBIE6Cg/gNr0NgNMX5Q2Rf5DqfcObpm980ojv5ZK09dk5ep+B1PxXMeC32m+r/vWki
         DWHTzAbh0RXCkGVfWtYCuOraCzKbq1HOjRIt6GGy7PNDGOCEhTTG5/vEI199E7Em4tfb
         9OXX9v1MxmG8V49/xMBOa2xzY6gW4AaDRb67k6Xcf9PWRH+/TsV0pEzLPI3JU1IQ4Cmo
         Bkr3YDxM32604B9oaqeM+eWW66mzWR/zZEcjvu9UMaD4AzF6V+cCIhVDG49Vnh6oautQ
         r6GYOAx6/liVGWIqUvo/NOUZsWXrTPvlRPGW7Afe5cHYUJ2+BkFgSc9vEZI0be+0wcOC
         SkPA==
X-Gm-Message-State: APjAAAXUoCad3J9/GrEsz7OlwWk+sHbBn876LRea23GrLutH3UuO2+c0
	xaU9be34dnU35Ya09Ws3iBlAPJHHT+vg7nq0xh5bmg==
X-Google-Smtp-Source: 
 APXvYqwLa2EK1I/UnbbvxRaeBKFESSPQQSbIApT4lwJ4pUKWK0CHoqWIhj6SVYuDxankfh6PmT7jSRppFHrbWtdMd0o=
X-Received: by 2002:ac2:4849:: with SMTP id 9mr3487692lfy.11.1574265748296;
 Wed, 20 Nov 2019 08:02:28 -0800 (PST)
MIME-Version: 1.0
References: <C558FB86-C340-4748-ABFF-118B0860C779@yesql.se>
In-Reply-To: <C558FB86-C340-4748-ABFF-118B0860C779@yesql.se>
From: Magnus Hagander <magnus@hagander.net>
Date: Wed, 20 Nov 2019 17:02:16 +0100
Message-ID: 
 <CABUevExw5FtjqcXZajcvyN9oBnUYZafPRtaSZcrBcg+r9ZtQ9g@mail.gmail.com>
Subject: Re: Odd markup in SSL mode table
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b5b0450597c94e12"
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

--000000000000b5b0450597c94e12
Content-Type: text/plain; charset="UTF-8"

On Wed, Nov 20, 2019 at 2:58 PM Daniel Gustafsson <daniel@yesql.se> wrote:

> In the SSL mode table (33.1), one of the "MITM Protection" values is set
> using
> <literal> while seemingly being normal text.  It has been like this since
> added
> in af2cf3be03f284aa12a07bce2b95d4a2768b290f, but I can't figure out why,
> and it
> makes it look odd IMO.
>
> Any reason not to apply the attached and remote the <literal> tags to make
> the
> row in question formatted like the other rows in the table?
>

No, that looks like a copy/paste error that has survived for 10 years.
Will apply.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 20, 2019 at 2:58 PM Danie=
l Gustafsson &lt;<a href=3D"mailto:daniel@yesql.se">daniel@yesql.se</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In the S=
SL mode table (33.1), one of the &quot;MITM Protection&quot; values is set =
using<br>
&lt;literal&gt; while seemingly being normal text.=C2=A0 It has been like t=
his since added<br>
in af2cf3be03f284aa12a07bce2b95d4a2768b290f, but I can&#39;t figure out why=
, and it<br>
makes it look odd IMO.<br>
<br>
Any reason not to apply the attached and remote the &lt;literal&gt; tags to=
 make the<br>
row in question formatted like the other rows in the table?<br></blockquote=
><div><br></div><div>No, that looks like a copy/paste error that has surviv=
ed for 10 years.=C2=A0 Will apply.</div></div><div><br></div>-- <br><div di=
r=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>=C2=A0Magnus Haga=
nder<br>=C2=A0Me: <a href=3D"http://www.hagander.net/" target=3D"_blank">ht=
tps://www.hagander.net/</a><br>=C2=A0Work: <a href=3D"http://www.redpill-li=
npro.com/" target=3D"_blank">https://www.redpill-linpro.com/</a></div></div=
></div></div>

--000000000000b5b0450597c94e12--