On 01/05/2014 03:11 PM, Greg Stark wrote:
On Fri, Jan 3, 2014 at 3:20 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
I think Florian has a good point there, and the reason is this: what
you are talking about will be of exactly zero use to applications that
want to see the results of one query before launching the next.
There are techniques for handling that actually. For a better
explanation than I can do see
http://kentonv.github.io/capnproto/rpc.html. It's mostly a language
feature but it does require support from the protocol to be able to
reference data in earlier responses in your subsequent requests.
Purely from a perspective of latency avoidance, sub-queries, WITH or
stored procedures can achieve the same thing, and work even if the
intermediate result has to undergo some transformation. :-)
--
Florian Weimer / Red Hat Product Security Team
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
