> The patch basically forces all use of libpq by dblink to be asynchronous > (internally) so that a cancel can be sensed and passed down to the > remote side and everything cleaned up. Possibly the right thing to do, > but dblink already allows the use of async queries, and the current > synchronous method uses standard libpq calls.
The point is *memory leak* in dblink when a query is canceled or become time-out. I think it is a bug, and my patch could fix it.
Regards, --- ITAGAKI Takahiro NTT Open Source Software Center