| From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: SELECT's take a long time compared to other DBMS |
| Date: | 2003-09-04 08:00:51 |
| Message-ID: | 3F573E8B.31916.A1063F8@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 4 Sep 2003 at 0:48, Relaxin wrote:
> All of the databases that I tested the query against gave me immediate
> access to ANY row of the resultset once the data had been returned.
> Ex. If I'm currently at the first row and then wanted to goto the 100,000
> row, I would be there immediately, and if I wanted to then goto the 5
> row...same thing, I have the record immediately!
>
> The other databases I tested against stored the entire resultset on the
> Server, I'm not sure what PG does...It seems that brings the entire
> resultset client side.
> If that is the case, how can I have PG store the resultset on the Server AND
> still allow me immediate access to ANY row in the resultset?
You can use a cursor and get only required rows.
Bye
Shridhar
--
Nick the Greek's Law of Life: All things considered, life is 9 to 5 against.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Relaxin | 2003-09-04 08:16:47 | Re: SELECT's take a long time compared to other DBMS |
| Previous Message | Relaxin | 2003-09-04 07:48:42 | Re: SELECT's take a long time compared to other DBMS |