As Kris said and I said. If your jvm crashes it's a jvm problem.
I know people that have queries that take 20 minutes or more...
On 22-Feb-08, at 3:39 PM, Andres Olarte wrote:
> I know it's the same to count 1 o 20M rows, but it takes much longer
> to count 20M. I really don't know much about the internal of the
> driver, but maybe some kind of time out?
> On Fri, Feb 22, 2008 at 2:33 PM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>> On Fri, 22 Feb 2008, Andres Olarte wrote:
>>> Just did a quick test with synthetic data (20M rows 3 columns:
>>> timestamp, and text). And it worked ok both on Java (with driver
>>> postgresql-8.1-407.jdbc3.jar) and PgAdmin.
>>> Perhaps you could try to build a test case to expose the problem?
>> From a client perspective, select count(*) should be the same no
>> how many rows there are and what types of columns are in the table,
>> so a
>> test case won't be helpful. If the JVM is just up and dying,
>> that's the
>> JVM's fault not a pg issue.
>> Kris Jurka
> ---------------------------(end of
> TIP 7: You can help support the PostgreSQL project by donating at
In response to
pgsql-jdbc by date
|Next:||From: shah exports||Date: 2008-02-23 13:15:09|
|Subject: Request for JDBC support|
|Previous:||From: Andres Olarte||Date: 2008-02-22 20:39:54|
|Subject: Re: JVM crash when select count(*) on large table through JDBC|