On 12/16/16 10:38 AM, Andrew Borodin wrote:
> 2016-12-16 20:17 GMT+05:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
>>> And one more thing... Can we have BackgroundSessionExecute() splitted
>>> into two parts: start query and wait for results?
>>> It would allow pg_background to reuse bgsession's code.
>>
>> Yes, I will look into that.
>
> Thank you. I'm marking both patches as "Waiting for author", keeping
> in mind that pg_background is waiting for bgsessions.
> After updates I'll review these patches.
New patch, mainly with the function split as you requested above, not
much else changed.
For additional entertainment, I include patches that integrate
background sessions into dblink. So dblink can open a connection to a
background session, and then you can use the existing dblink functions
to send queries, read results, etc. People use dblink to make
self-connections to get autonomous subsessions, so this would directly
address that use case. The 0001 patch is some prerequisite refactoring
to remove an ugly macro mess, which is useful independent of this. 0002
is the actual patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
