From: Tom Lane t...@sss.pgh.pa.us
I just noticed this CF entry pertaining to the same problem that Stephen
Frost reported a couple days ago:
http://www.postgresql.org/message-id/20140211205336.gu2...@tamriel.snowman.net
I believe it's been adequately fixed as of commits fa4440f516 and
MauMau maumau...@gmail.com writes:
If the backend is terminated with SIGKILL while psql is running \copy
table_name from file_name, the \copy didn't end forever. I expected \copy
to be cancelled because the corresponding server process vanished.
I just noticed this CF entry pertaining to
On 20 December 2013 19:43, MauMau Wrote
[Problem]
If the backend is terminated with SIGKILL while psql is running \copy
table_name from file_name, the \copy didn't end forever. I expected
\copy
to be cancelled because the corresponding server process vanished.
[Cause]
psql could not
From: Dilip kumar dilip.ku...@huawei.com
Is there any direct scenario by which it can be reproduce ?
Thank you for reviewing and testing the patch. There is no other direct
scenario.
I reproduced the failure exactly like you suggested, because it was very
difficult to reproduce the problem
Hello,
I've encountered a bug on PG 9.2 and fixed it for 9.4. Please find attached
the patch. I'd like it to be backported to at least 9.2.
[Problem]
If the backend is terminated with SIGKILL while psql is running \copy
table_name from file_name, the \copy didn't end forever. I expected
