From: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Pgsql-Performance <pgsql-performance@postgresql.org>
Subject: Re: Can this query go faster???
Date: Tue, 06 Dec 2005 11:21:00 +0100
Message-ID: <1133864460.8837.69.camel@Panoramix> (raw)
In-Reply-To: <1133862777.4779.185.camel@coppola.muc.ecircle.de>
References: <1133862229.8837.61.camel@Panoramix>
<1133862777.4779.185.camel@coppola.muc.ecircle.de>
On Tue, 2005-12-06 at 10:52 +0100, Csaba Nagy wrote:
> Joost,
>
> Why do you use an offset here ? I guess you're traversing the table
> somehow, in this case it would be better to remember the last zipcode +
> housenumber and put an additional condition to get the next bigger than
> the last one you've got... that would go for the index on
> zipcode+housenumber and be very fast. The big offset forces postgres to
> traverse that many entries until it's able to pick the one row for the
I am forced to translate a sorting dependent record number to a record
in the database. The GUI (a Java JTable) works with record /row numbers,
which is handy if one has an ISAM database, but not if one uses
PostgreSQL.
I wonder if using a forward scrolling cursor would be faster.
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl
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: J.Kraaijeveld@Askesis.nl, nagy@ecircle-ag.com
Subject: Re: Can this query go faster???
In-Reply-To: <1133864460.8837.69.camel@Panoramix>
* 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