On Wed, Feb 09, 2011 at 10:55:05AM +0900, Itagaki Takahiro wrote:
On Mon, Feb 7, 2011 at 22:47, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On Mon, Feb 7, 2011 at 21:17, Noah Misch n...@leadboat.com wrote:
The message does not show which foreign table yielded the error.
On Mon, Feb 7, 2011 at 22:47, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On Mon, Feb 7, 2011 at 21:17, Noah Misch n...@leadboat.com wrote:
The message does not show which foreign table yielded the error. We could
evade
the problem in this case by adding a file name to the
Suppose you create several file_fdw foreign tables, query them together, and
read(2) returns EIO for one of the files:
[local] postgres=# SELECT * FROM ft0, ft1, ft2;
ERROR: could not read from COPY file: Input/output error
The message does not show which foreign table yielded the error. We
On 07.02.2011 14:17, Noah Misch wrote:
Suppose you create several file_fdw foreign tables, query them together, and
read(2) returns EIO for one of the files:
[local] postgres=# SELECT * FROM ft0, ft1, ft2;
ERROR: could not read from COPY file: Input/output error
The message does not show
