Hi, On 2018-03-28 16:29:37 +0800, Craig Ringer wrote: > > - allow *streaming* of large datums > > Yes, very much +1 there. That's already on the wiki. Yeah: > > * Permit lazy fetches of large values, at least out-of-line TOASTED values > http://www.postgresql.org/message-id/53ff0ef8....@2ndquadrant.com
That's not necessarily the same though. What I think we need is the ability to have "chunked" encoding with *optional* length for the overall datum. And then the backend infrastructure to be able to send *to the wire* partial datums. Probably with some callback based StringInfo like buffer. > - nested table support > > > > > Can you elaborate on that one? Nested recordsets. E.g. a SRF or procedure returning multiple query results. > * room for other resultset formats later. Like Damir, I really want to add > protobuf or json serializations of result sets at some point, mainly so we > can return "entity graphs" in graph representation rather than left-join > projection. -1. I don't think this belongs in postgres. Greetings, Andres Freund
