Re: Can this query go faster???
От | Joost Kraaijeveld |
---|---|
Тема | Re: Can this query go faster??? |
Дата | |
Msg-id | 1133864460.8837.69.camel@Panoramix обсуждение исходный текст |
Ответ на | Re: Can this query go faster??? (Csaba Nagy <nagy@ecircle-ag.com>) |
Ответы |
Re: Can this query go faster???
|
Список | pgsql-performance |
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
В списке pgsql-performance по дате отправления: