From: Oliver Jowett <oliver@opencloud.com>
To: Bill Chandler <billybobc1210@yahoo.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-jdbc@postgresql.org
Subject: Re: Cursors performance
Date: Sat, 10 Jul 2004 09:55:35 +1200
Message-ID: <40EF1457.1060002@opencloud.com> (raw)
In-Reply-To: <20040709202416.54013.qmail@web51401.mail.yahoo.com>
References: <20040709202416.54013.qmail@web51401.mail.yahoo.com>
Bill Chandler wrote:
> Now the mystery is why is this happening all of the
> sudden? I have been running w/ fetch size set to 5000
> for the last couple of weeks and it did not appear to
> be doing this (i.e. re-running the entire select
> statement again). Is this what I should expect when
> using cursors? I would have thought that the server
> should "remember" where it left off in the query since
> the last fetch and continue from there.
I'd check heap size, GC activity (-verbose:gc), CPU use, swapping
activity on the *client* side. It may be that your dataset size or
physical memory or something similar has changed sufficiently that GC
resulting from the data in each 5k row batch is killing you.
Can you try a trivial app that runs the same query (with same fetchsize,
autocommit, etc) via JDBC and does nothing but steps forward through the
resultset, and see how fast it runs? Perhaps the problem is in your
processing logic.
-O
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: oliver@opencloud.com, billybobc1210@yahoo.com, pgsql-jdbc@postgresql.org
Subject: Re: Cursors performance
In-Reply-To: <40EF1457.1060002@opencloud.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox