| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Stefan Reiser <s(dot)reiser(at)tu-braunschweig(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zelaine(at)amazon(dot)com, pgsql-bugs(at)postgresql(dot)org, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Date: | 2013-01-11 17:23:18 |
| Message-ID: | alpine.BSO.2.00.1301111221410.28737@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
On Fri, 11 Jan 2013, Dave Cramer wrote:
> Ok, I've pushed this fix into master
>
You've made any failure to parse the affected row count return
SUCCESS_NO_INFO. Shouldn't you change the integer parsing to a long
parsing and only modify the response if the value is > INT_MAX while still
throwing an exception if we get something that is truly undecipherable?
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Reiser | 2013-01-11 17:36:02 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Previous Message | Kris Jurka | 2013-01-11 17:21:37 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Reiser | 2013-01-11 17:36:02 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |
| Previous Message | Kris Jurka | 2013-01-11 17:21:37 | Re: [BUGS] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception |