Re: Large tables, ORDER BY and sequence/index scans

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Milan Zamazal <pdm(at)brailcom(dot)org>
Cc: Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Large tables, ORDER BY and sequence/index scans
Date: 2010-01-05 13:38:03
Message-ID: 2f4958ff1001050538h37ddd660m5f973d25e28a4221@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/1/5 Milan Zamazal <pdm(at)brailcom(dot)org>:

> Cursors are very convenient for me, because they allow easy browsing
> data in the user interface (fetching limited sets of rows while seeking
> forward and backward) and they prevent contingent seeking and other
> troubles when concurrent updates happen.
>

Sounds to me like a borked app design. Do you seriously need to walk
the user through couple of million rows of data ?

I mean, databases are designed to work on data, and give you the
result back. Use this capability intelligently.

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2010-01-05 13:45:01 Re: Large tables, ORDER BY and sequence/index scans
Previous Message Albe Laurenz 2010-01-05 13:35:06 Re: Large tables, ORDER BY and sequence/index scans