Robert Haas <[email protected]> wrote: > I'm pretty sure it's the same as this: > https://commitfest.postgresql.org/action/patch_view?id=263
Yes, (2) are resolved with the patch with a different implementation. > (2) is fixed by RegisterXactCallback(AtEOXact_dblink). However, there > might be any better solutions -- for example, ResourceOwner framework. (1) still exists, but we had a consensus that we don't have to fix it because we have async functions. > (1) is fixed by using non-blocking APIs in libpq. I think we should > always use non-blocking APIs even if the dblink function itself is > a blocking-function. Regards, --- Takahiro Itagaki NTT Open Source Software Center -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
