results in
potentially very large memory use by such queries. (Per-
row memory is not freed until the statement completes.)
My reading of the todo list is that this is a known bug
(or feature!).
BTW: Does anyone know if there are plans to fix this one soon?
Mike Beller
Barnes wrote:
>
Folks--
Thanks for the ideas. But bisection just seemed too cumbersome.
In the end I decided to write a data filter in perl which checks
all the data for valid types before putting it into the DB!
Mike
Ed Loehr wrote:
>
> I have found that judicious placement of a few queries (selects, inten
rd_att->attrs[i]->attbyval))
elog(ERROR, "copy from line %d: Bad file format",
lineno);
So the lineno information is there, it's just not available when pg_atoi
logs its error and bails out.
Is it possible for pg_atoi to return an invalid pointer instead
of completely bailing out, thus allowing the 'sanity check' code
to print the line number? I have no idea how many things this
might break...
Regards
Mike Beller
CTO
Tradeworx.com
