Re: Performance problem with timestamps in result sets - Mailing list pgsql-jdbc

From Thomas Dudziak
Subject Re: Performance problem with timestamps in result sets
Date
Msg-id 224f32340603080657m35f7c35do34a2c6dc3f1b5f0@mail.gmail.com
Whole thread Raw
In response to Re: Performance problem with timestamps in result sets  ("Michael Paesold" <mpaesold@gmx.at>)
Responses Re: Performance problem with timestamps in result sets
List pgsql-jdbc
On 3/8/06, Michael Paesold <mpaesold@gmx.at> wrote:

> This should be 1 ms per getTimestamp call, shouldn't it? The time is the
> aggregate time for ~8000 calls. That is still rather slow, yeah, but it is
> so with profiling.

Yep, but as I said, the others are much faster. E.g. getString takes
140ms for 5460 calls, and getInt 570ms for 10920 calls, so its
probably not so much the profiler.
Also, I was merely asking whether there is something that could be
done to bring getTimestamp at least in the same region.

cheers,
Tom

pgsql-jdbc by date:

Previous
From: "Michael Paesold"
Date:
Subject: Re: Performance problem with timestamps in result sets
Next
From: Oliver Jowett
Date:
Subject: Re: Performance problem with timestamps in result sets