Re: [HACKERS] libpq: why we need to fetch all rows? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] libpq: why we need to fetch all rows?
Date
Msg-id 220f7c766162df1fc600ebb9695818e3
Whole thread Raw
In response to [HACKERS] libpq: why we need to fetch all rows?  (Alexander Demenshin <aldem@techie.com>)
List pgsql-hackers
>
> Not necessarily. A join could produce some sort of temporary table (disk
> based or in memory) and each row produced by the join assigned an Oid.

True, in fact, I am working on the sort code now.  However, if there is
an order by, you have to get all the rows and sort them, before
returning any of them.  How many of these queries don't have an order
by?  Usually most multi-row results have one.

- --
Bruce Momjian
maillist@candle.pha.pa.us

------------------------------

pgsql-hackers by date:

Previous
From: Igor
Date:
Subject: Re: [HACKERS] libpq: why we need to fetch all rows?
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] libpq: why we need to fetch all rows?