From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christoffer Gurell <orbit(at)0x63(dot)nu>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: number of rows in a cursor |
Date: | 2004-02-10 16:47:30 |
Message-ID: | Pine.LNX.4.33.0402100947110.28531-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 10 Feb 2004, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Christoffer Gurell wrote:
> >> After declaring a cursor. Is there any way you can check the number of rows
> >> that cursor contains ??
>
> > Yes, you can MOVE ALL in the cursor and look at the return status,
>
> Note however that this is *not* a cheap operation. You might as well
> fetch the data, because it's going to cost nearly as much as FETCH.
>
> (Worse, in pre-7.4 versions, MOVE BACKWARDS ALL is also nearly as
> expensive as FETCH, so that getting the number of rows and then fetching
> the data will cost you close to 3x the runtime of the FETCH alone.)
At that point wouldn't a select count(*) from table where...
be cheaper?
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-02-10 16:50:31 | Re: I want to use postresql for this app, but... |
Previous Message | Steve Crawford | 2004-02-10 16:47:16 | Re: I want to use postresql for this app, but... |