Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1n9XHM-0007la-QD
	for pgsql-docs@arkaria.postgresql.org; Mon, 17 Jan 2022 19:02:56 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1n9XHK-0005bx-Bi
	for pgsql-docs@arkaria.postgresql.org; Mon, 17 Jan 2022 19:02:54 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1n9XHK-0005bo-4B
	for pgsql-docs@lists.postgresql.org; Mon, 17 Jan 2022 19:02:54 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1n9XHE-0005zX-Vz
	for pgsql-docs@lists.postgresql.org; Mon, 17 Jan 2022 19:02:53 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 20HJ2j05046046;
	Mon, 17 Jan 2022 14:02:47 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: koizumistr@minos.ocn.ne.jp
cc: pgsql-docs@lists.postgresql.org
Subject: Re: missing a white space in the last sentence of 51.6. Executor
In-reply-to: <164242945435.31951.14375506753598286638@wrigleys.postgresql.org>
References: <164242945435.31951.14375506753598286638@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Mon, 17 Jan 2022 14:24:14 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46044.1642446165.1@sss.pgh.pa.us>
Date: Mon, 17 Jan 2022 14:02:45 -0500
Message-ID: <46045.1642446165@sss.pgh.pa.us>
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>
Archived-At: 
 <https://www.postgresql.org/message-id/46045.1642446165%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> The last sentence of 51.6. Executor appears:
> "...feeding that up toModifyTable to perform the insertion."

Hm, the space is definitely there in the source file:

    A simple <command>INSERT ... VALUES</command> command creates a
    trivial plan tree consisting of a single <literal>Result</literal>
    node, which computes just one result row, feeding that up
    to <literal>ModifyTable</literal> to perform the insertion.

I also see it rendered properly in HTML when looking at a local docs
build.  I think this is some sort of spacing issue in the website
style sheets.  Other <literal> segments on the same page are also
rendered with less-than-usual spacing around them (to my eye
anyway); though this is the only one that looks like it has no
space at all.

			regards, tom lane