pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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
Date: Mon, 17 Jan 2022 14:02:45 -0500
Message-ID: <46045.1642446165@sss.pgh.pa.us> (raw)
In-Reply-To: <164242945435.31951.14375506753598286638@wrigleys.postgresql.org>
References: <164242945435.31951.14375506753598286638@wrigleys.postgresql.org>

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





view thread (3+ messages)  latest in thread

Message-ID: <46045.1642446165@sss.pgh.pa.us>
Permalink:  ../46045.1642446165@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/46045.1642446165@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, koizumistr@minos.ocn.ne.jp, pgsql-docs@lists.postgresql.org
  Subject: Re: missing a white space in the last sentence of 51.6. Executor
  In-Reply-To: <46045.1642446165@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox