Re: Adding a note to protocol.sgml regarding CopyData - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Adding a note to protocol.sgml regarding CopyData
Date
Msg-id f5947186-5e94-f3af-de3a-27a5b83469a7@2ndquadrant.com
Whole thread Raw
In response to Re: Re[2]: Adding a note to protocol.sgml regarding CopyData  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Adding a note to protocol.sgml regarding CopyData  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 25/09/2018 13:55, Amit Kapila wrote:
> On Tue, Sep 25, 2018 at 4:51 AM Bradley DeJong <bpd0018@gmail.com> wrote:
>>
>> On 2018-09-22, Amit Kapila wrote ...
>>  > ... duplicate the same information in different words at three
>> different places ...
>>
>> I count 7 different places. In the protocol docs, there is the old
>> mention in the "Summary of Changes since Protocol 2.0" section
>>
> 
> Below text is present in the section quoted by you:
> The special <quote><literal>\.</literal></quote> last line is not
> needed anymore, and is not sent during <command>COPY OUT</command>.
> (It is still recognized as a terminator during <command>COPY
> IN</command>, but its use is deprecated and will eventually be
> removed.)
> 
> This email started with the need to mention this in protocol.sgml and
> it is already present although at a different place than the place at
> which it is proposed.  Personally, I don't see the need to add it to
> more places.  Does anybody else have any opinion on this matter?

Yeah, I don't see why we need to document it three times in the same
chapter.

Also, that chapter is specifically about version 3.0 of the protocol, so
documenting version 2.0 is out of scope.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Making all nbtree entries unique by having heap TIDs participatein comparisons
Next
From: James Robinson
Date:
Subject: Pithy patch for more detailed error reporting wheneffective_io_concurrency is set to nonzero on platforms lackingposix_fadvise()