On Fri, 11 Jan 2013, Dave Cramer wrote:
> Ok, I've pushed this fix into master > You've made any failure to parse the affected row count return SUCCESS_NO_INFO. Shouldn't you change the integer parsing to a long parsing and only modify the response if the value is > INT_MAX while still throwing an exception if we get something that is truly undecipherable? Kris Jurka -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
