On Tue, May 16, 2017 at 6:29 PM, Vaishnavi Prabakaran <vaishnaviprabaka...@gmail.com> wrote: > On Tue, May 16, 2017 at 8:40 AM, Thomas Munro > <thomas.mu...@enterprisedb.com> wrote: >> >> >> I you hit ^d while COPY FROM STDIN is reading then subsequent COPY >> FROM STDIN commands return immediately. > > > Hi, I could not reproduce this issue. Even after Ctrl+d , subsequent COPY > from commands reads the input properly. Is there any specific step you > followed or can you share the sample testcase?
Hmm. Doesn't happen on GNU/Linux, does happen on macOS and FreeBSD. Example: postgres=# create table t(a int); CREATE TABLE postgres=# copy t(a) from stdin; Enter data to be copied followed by a newline. End with a backslash and a period on a line by itself. >> 42 >> [...press ^d here ...]COPY 1 postgres=# copy t(a) from stdin; Enter data to be copied followed by a newline. End with a backslash and a period on a line by itself. >> COPY 0 -- Thomas Munro http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers