Thread: Bad integer

I'm getting "Bad integer 4020239173" error. From what I found on the
  Web it seems to be a Postgres bug, not specific to any programming
  language. I've found PHP and Java guys complaining about it (I'm
  using JDBC). However, I failed to find resolution of this problem.
  Can you suggest something?

--
Best regards,
 Dmitry                          mailto:dmacsema@iname.com

Dmitry Macsema <dmacsema@iname.com> writes:
>   I'm getting "Bad integer 4020239173" error. From what I found on the
>   Web it seems to be a Postgres bug, not specific to any programming
>   language.

First I've heard of it.  You're going to have to provide a lot more
information if you want us to believe it's a Postgres problem.

The only occurrence of the string "bad integer" in current postgres
sources is

src/interfaces/jdbc/org/postgresql/errors.properties: postgresql.res.badint:Bad Integer {0}

which appears to be an exception thrown only by toInt().  Complaining
because someone tried to coerce an oversize value to integer is not
obviously a bug...

            regards, tom lane