The bug is in the ODBC driver: it shouldn't be using int4out() inthe first place. This has been fixed for awhile; please updateyour ODBC driver.
regards, tom lane