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

From Tom Lane
Subject Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Date
Msg-id 17929.1356108458@sss.pgh.pa.us
Whole thread Raw
Responses Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
zelaine@amazon.com writes:
> The following bug has been logged on the website:
> Bug reference:      7766
> Logged by:          Zelaine Fong
> Email address:      zelaine@amazon.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


pgsql-jdbc by date:

Previous
From: "Hudson, Derrick"
Date:
Subject: Re: JPA + enum == Exception
Next
From: Dave Cramer
Date:
Subject: Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception