Re: [HACKERS] COPY FROM STDIN behaviour on end-of-file - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] COPY FROM STDIN behaviour on end-of-file
Date
Msg-id CA+TgmoYZSkn5iGkLCnQJZ7c_2syEchric9-42CyPSWF94r0B3w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] COPY FROM STDIN behaviour on end-of-file  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] COPY FROM STDIN behaviour on end-of-file  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 16, 2017 at 1:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
>> I had been supposing that this was a feature addition and should be left
>> for the next commitfest.  But given that it already works as-expected on
>> popular platform(s), the fact that it doesn't work the same on some other
>> platforms seems like a portability bug rather than a missing feature.
>> Now I'm inclined to treat it as a bug and back-patch.
>
> BTW, the main argument for considering it a new feature is that we don't
> suggest anywhere in our code or docs that this will work.  If we're going
> to go out of our way to make it work, should we mention it in psql-ref?
> And what about changing the interactive prompt, along the lines of
>
> End with a backslash and a period on a line by itself, or an EOF signal.

Well, the current behavior is so wonky and inconsistent that it's hard
for me to view it as anything but a bug.  I mean, one can argue about
exactly what an EOF should do in any given situation, but surely it
can't be right for it to do one thing on one platform and something
else on a different platform.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Relcache leak when row triggers on partitions are firedby COPY
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] COPY FROM STDIN behaviour on end-of-file