Re: Prepared select - Mailing list pgsql-hackers

From Robert Turnbull
Subject Re: Prepared select
Date
Msg-id 002b01c425a8$009d78b0$7e02a8c0@robert
Whole thread Raw
In response to Re: Prepared select  (Christoph Haller <ch@rodos.fzk.de>)
List pgsql-hackers
There are several production issues related to the proposed solution. For
example, what happens when the result set exceeds the swap space of the
server or client machine? My original question is how to get a cursor from a
prepared select so a subset of the result can be returned to the client for
processing. For your solution to work the SQL EXECUTE command needs the
functionality of  the SQL FETCH command.


> >
> >
> > How can I use a prepared select statement as mentioned in the
documentation=
> >  on SQL PREPARE. Preparing the statement is easy, the problem is using
the =
> > plan to get a cursor. My assumption is the SQL OPEN command is not
document=
> > ed or there is some other libpq API to make this happen.
> >
> > Thanks
> >
> >
> >
> I'm using libpq and lines like below are working:
>
> res = PQexec(conn,
> "PREPARE plan001 ( integer , double precision , character ) AS SELECT
a,b,d FROM foo WHERE a = $1 OR d > $2 OR b = $3");
> ...
> res = PQexec(conn, "EXECUTE plan001 ( 3 , 6.66 , 'whatever' ) ");
>
> HTH, pretty late reply - I know (but no one else did as far as I can tell)
>
> Regards, Christoph
>
>
>



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: ERROR action extension for rules?
Next
From: Kenneth Marshall
Date:
Subject: Re: Why are these ARC variables per-backend?