From: Tom Lane <tgl@sss.pgh.pa.us>
To: bryn@yugabyte.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Proposal to improve the content in subsection 8.16.6. "Composite
 Type Input and Output Syntax"
In-reply-to: <158593753274.7901.11178770123847486396@wrigleys.postgresql.org>
References: <158593753274.7901.11178770123847486396@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Fri, 03 Apr 2020 18:12:12 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23092.1585952196.1@sss.pgh.pa.us>
Date: Fri, 03 Apr 2020 18:16:36 -0400
Message-ID: <23093.1585952196@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> 1. Replace this:
> "...the whitespace will be ignored if the field type is integer, but not if
> it is text."
> with this:
> "...the whitespace will be ignored if the field type is integer, but not if
> it is a character data type like text."

It's already an example, so I don't see this as an improvement.

> Insert this between the two sentences, i.e. after "...any individual field
> value." and before "You must do so if...":

The proposed additional text is flat-out wrong.

What actually happens here is that text between quotes is considered
quoted (so that, for example, commas within it are not field separators),
but that does not exclude there being other unquoted text within the
same field value.

			regards, tom lane