Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
| От | Dave Cramer |
|---|---|
| Тема | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Дата | |
| Msg-id | CADK3HH+JgxrrT7K7tbyHLT0pqqnmqQNoPC6keHV3uChRq1ah4w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
|
| Список | pgsql-jdbc |
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
On Fri, Dec 21, 2012 at 11:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
В списке pgsql-jdbc по дате отправления: