| From: | Harald Fuchs <hf0923x(at)protecting(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: partial resultset in java |
| Date: | 2006-03-22 14:44:02 |
| Message-ID: | 87fylafsjx.fsf@srv.protecting.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In article <b80d582c0603212153p654d0f06t4ddfec76ada2bfce(at)mail(dot)gmail(dot)com>,
Luckys <plpgsql(at)gmail(dot)com> writes:
> I believe you should restrict number of rows that needs to be returned, or
> giving a choice to the user, although showing the total count. Even if you
> display all 20K records, no one is going to see them all, you can even add
> one more LIKE condition to match the user's criteria.
I second that. Whenever you connect an interactive application to a
DB backend and you don't know in advance some upper limit for the
number of rows returned by a query, append a "LIMIT 1000" or something
like that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emi Lu | 2006-03-22 14:44:03 | about "explain analyze" cannot get detailed analyzed results for queries in a plpgsql function |
| Previous Message | Tom Lane | 2006-03-22 14:40:15 | Re: pg 8.1.3 on AIX |