| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | zelaine(at)amazon(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Date: | 2012-12-21 16:47:38 |
| Message-ID: | 17929.1356108458@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | me | 2012-12-21 17:08:27 | BUG #7768: Support for TCP Keepalive parameters |
| Previous Message | Heikki Linnakangas | 2012-12-21 13:38:10 | Re: pg_basebackup fails if a data file is removed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2012-12-21 18:55:43 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Previous Message | zelaine | 2012-12-20 19:23:13 | BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |