Re: select limit error in file_fdw
Erik Rijkers <er@xs4all.nl>
From: Erik Rijkers <er@xs4all.nl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2018-12-16T16:45:58Z
Lists: pgsql-hackers
On 2018-12-16 16:52, Tom Lane wrote: > Erik Rijkers <er@xs4all.nl> writes: >> On 2018-12-16 07:03, Tom Lane wrote: >>> Um ... this example works for me, in both HEAD and v11 branch tip. >>> Moreover, the behavior you describe is exactly what ffa4cbd623 was >>> intended to fix. Is there any chance that you got 11.1 and v11 >>> branch tip mixed up? > >> [ nope ] >> On the other hand, in that test.sh, have you tried enlarging the test >> table? > > Yeah, I tried sizes ranging up to 1m tuples without success. > > However, something else occurred to me this morning, and a bit > later I can reproduce the problem! I did it by changing the > table's definition to use a shell pipeline: > > program 'unzip -p \"/tmp/t.zip\" \"tmp/t.txt\" | cat' > > ERROR: program "unzip -p "/tmp/t.zip" "tmp/t.txt" | cat" failed > DETAIL: child process exited with exit code 141 curious... Adding that ' | cat' tail makes all 3 instances (that I have tried) fail: 11.1 as released, REL_11_STABLE, and instance from d56e0fde /bin/sh seems to be dash, here. bash version is: $ /bin/bash --version GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
Commits
-
Improve detection of child-process SIGPIPE failures.
- b1894a6076f3 11.2 landed
- ade2d61ed09c 12.0 landed
- 34010ac2fa18 10.7 landed
-
Handle EPIPE more sanely when we close a pipe reading from a program.
- ffa4cbd623dd 12.0 cited