Tom Lane 6f922ef88e Improve efficiency of dblink by using libpq's new row processor API. ... This patch provides a test case for libpq's row processor API. contrib/dblink can deal with very large result sets by dumping them into a tuplestore (which can spill to disk) --- but until now, the intermediate storage of the query result in a PGresult meant memory bloat for any large result. Now we use a row processor to convert the data to tuple form and dump it directly into the tuplestore. A limitation is that this only works for plain dblink() queries, not dblink_send_query() followed by dblink_get_result(). In the latter case we don't know the desired tuple rowtype soon enough. While hack solutions to that are possible, a different user-level API would probably be a better answer. Kyotaro Horiguchi, reviewed by Marko Kreen and Tom Lane		2012-04-04 18:39:08 -04:00
..
src	Improve efficiency of dblink by using libpq's new row processor API.	2012-04-04 18:39:08 -04:00
bug.template	Stamp HEAD as 9.2devel.	2011-06-11 17:46:49 -04:00
KNOWN_BUGS
Makefile
MISSING_FEATURES
TODO