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

From Tom Lane
Subject Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Date
Msg-id 6059.1356121026@sss.pgh.pa.us
Whole thread Raw
In response to Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-bugs
Dave Cramer <pg@fastcrypt.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


pgsql-bugs by date:

Previous
From: Dave Cramer
Date:
Subject: Re: [JDBC] BUG #7766: Running a DML statement that affects more than 4 billion rows results in an exception
Next
From: Andres Freund
Date:
Subject: Re: BUG #7763: "CREATE TABLE ... (LIKE ... INCLUDING INDEXES ...)" does not work with indexes on composite types