Re: shouldn't postgres know the numer of rows in a (sorted)

From: Richard Huxton <dev(at)archonet(dot)com>
To: Thies C Arntzen <thies(at)thieso(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: shouldn't postgres know the numer of rows in a (sorted)
Date: 2005-11-16 13:07:55
Message-ID: 437B2F2B.90402@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thies C Arntzen wrote:
> i would be interested in getting this uncorrected count "after sort"
> but "before first row" in query (a). so in a fresh DB with no
> updates/deletes this would be the correct count, and i could avoid the
> very expensive (b).

You don't say what applicaton language you are using, but most offer a
pg_num_rows() interface which tells you how many results are in the
recordset you have fetched.

Your best bet to learn more is to read whatever documentation comes with
your client library.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Presber 2005-11-16 13:16:08 Re: Tsearch2: casting text to tsquery
Previous Message Oleg Bartunov 2005-11-16 12:52:47 Re: Tsearch2: casting text to tsquery