Thomas Munro writes:
> On Wed, May 17, 2017 at 2:39 PM, Tom Lane wrote:
>> Thanks for checking. So that's two major platforms where it works "as
>> expected" already.
> Ah... the reason this is happening is that BSD-derived fread()
> implementations return immediately if the EOF flag is set[1],
On Wed, May 17, 2017 at 2:39 PM, Tom Lane wrote:
> Vaishnavi Prabakaran writes:
>>> Tom Lane wrote:
BTW, it would be a good idea for somebody to check this out on Windows,
assuming there's a way to generate a keyboard EOF signal there.
>
>> Ctrl-Z + Enter in windows generates EOF signal
Vaishnavi Prabakaran writes:
>> Tom Lane wrote:
>>> BTW, it would be a good idea for somebody to check this out on Windows,
>>> assuming there's a way to generate a keyboard EOF signal there.
> Ctrl-Z + Enter in windows generates EOF signal. I verified this issue and
> it is not reproducible in w
On Wed, May 17, 2017 at 3:52 AM, Alvaro Herrera
wrote:
> Tom Lane wrote:
>
> > BTW, it would be a good idea for somebody to check this out on Windows,
> > assuming there's a way to generate a keyboard EOF signal there.
>
> I last used a Windows command line almost two decades ago now, but
> Ctrl-
Tom Lane wrote:
> BTW, it would be a good idea for somebody to check this out on Windows,
> assuming there's a way to generate a keyboard EOF signal there.
I last used a Windows command line almost two decades ago now, but
Ctrl-Z used to do it.
--
Álvaro Herrerahttps://www.2ndQu
Robert Haas writes:
> On Tue, May 16, 2017 at 1:29 PM, Tom Lane 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
On Tue, May 16, 2017 at 1:29 PM, Tom Lane 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
>> platfo
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 f
Thomas Munro writes:
> On Tue, May 16, 2017 at 6:29 PM, Vaishnavi Prabakaran
> wrote:
>> 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. D
On Tue, May 16, 2017 at 6:29 PM, Vaishnavi Prabakaran
wrote:
> On Tue, May 16, 2017 at 8:40 AM, Thomas Munro
> 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+
On Tue, May 16, 2017 at 8:40 AM, Thomas Munro 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 sp
Hi hackers,
I you hit ^d while COPY FROM STDIN is reading then subsequent COPY
FROM STDIN commands return immediately. That's because we never clear
the end-of-file state on the libc FILE. Shouldn't we do that, perhaps
with something like the attached?
--
Thomas Munro
http://www.enterprisedb.c
12 matches
Mail list logo