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

From: Péter Kovács <peter(dot)dunay(dot)kovacs(at)gmail(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: zelaine(at)amazon(dot)com, pgsql-jdbc(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Date: 2013-01-12 09:27:22
Message-ID: CAO01x1FVYBEmywTST+Wkg02xSA=+hdcZiJysm1PtVuh7WHf4=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

I mean what value this method will return for an update statement
affecting, say, five billion rows? But I may misunderstand something.
On Jan 12, 2013 9:57 AM, "Dave Cramer" <pg(at)fastcrypt(dot)com> wrote:

> Peter,
>
> Can you be more specific about your concerns ?
>
> Dave
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Sat, Jan 12, 2013 at 3:25 AM, Péter Kovács <
> peter(dot)dunay(dot)kovacs(at)gmail(dot)com> wrote:
>
>> And what about
>> http://docs.oracle.com/javase/6/docs/api/java/sql/Statement.html#getUpdateCount()?
>>
>> P.
>> On Jan 11, 2013 2:20 PM, "Dave Cramer" <pg(at)fastcrypt(dot)com> wrote:
>>
>>> Ok, this is much more difficult than I thought.
>>>
>>> Turns out that there are at least two interfaces that expect an int not
>>> a long.
>>>
>>> BatchUpdateException
>>> executeBatch
>>>
>>> I'm thinking the only option here is to report INT_MAX as opposed to
>>> failing.
>>>
>>> Thoughts ?
>>>
>>> Dave
>>>
>>>
>>> Dave Cramer
>>>
>>> dave.cramer(at)credativ(dot)ca
>>> http://www.credativ.ca
>>>
>>>
>>> On Fri, Dec 21, 2012 at 3:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>
>>>> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>>>> > 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.
>>>>
>>>> I think we'll all be safely dead by the time anybody manages to process
>>>> 2^63 rows in one PG command ;-). If you can widen the value from int to
>>>> long on the Java side, that should be sufficient.
>>>>
>>>> regards, tom lane
>>>>
>>>
>>>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Cramer 2013-01-12 09:41:23 Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Previous Message Dave Cramer 2013-01-12 08:57:26 Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2013-01-12 09:41:23 Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Previous Message Dave Cramer 2013-01-12 08:57:26 Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception