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 73c85788cc8e9c4ba761aaba36250bb6
Whole thread Raw
In response to [HACKERS] libpq: why we need to fetch all rows?  (Alexander Demenshin <aldem@techie.com>)
List pgsql-hackers
>
> On Sun, 29 Jun 1997, Bruce Momjian wrote:
>
> > > statements. A lookup table of portals/cursors and their corresponding Oid
> > > tables could be maintained by the server.
> >
> > The problem is that most results are joins, and there are multiple oid's
> > to deal with .
>
> In this case couldn't you create a temporary table and return the name
> of the table to the client?  It could then "cursor" through the temporary
> table.

Yes, we could, but you would not want to do that all the time because of
performance.  You would have to determine if that particulary select
statement was going to need it.

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

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

pgsql-hackers by date:

Previous
From: "Michael J. Miller Jr."
Date:
Subject: Re: [HACKERS] libpq: why we need to fetch all rows?
Next
From: "Michael J. Miller Jr."
Date:
Subject: Re: [HACKERS] libpq: why we need to fetch all rows?