Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception

Thanks Tom.

So an unsigned long won't fit inside a java long either, but hopefully it
will never be necessary. That would be a huge number of changes.

Dave

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Fri, Dec 21, 2012 at 11:47 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> zelaine(at)amazon(dot)com writes:
> > The following bug has been logged on the website:
> > Bug reference: 7766
> > Logged by: Zelaine Fong
> > Email address: zelaine(at)amazon(dot)com
> > PostgreSQL version: 8.4.0
> > Operating system: Linux
> > Description:
>
> > The updateCount field in the ResultHandler interface in Java is defined
> as
> > an int rather than long. Therefore, if you prepare and execute an
> update,
> > delete, or insert statement that affects more than 2^32 rows, you will
> get
> > the following exception:
>
> > Unable to interpret the update count in command completion tag
>
> Forwarding this to pgsql-jdbc list. FWIW, guys, the backend currently
> thinks that execution counts are unsigned ints. So I surmise that the
> problematic update count was actually between 2^31 and 2^32. We might
> get around to changing it to unsigned long someday ...
>
> regards, tom lane
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>