Re: query cancel issues in contrib/dblink - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: query cancel issues in contrib/dblink
Date
Msg-id 20100225094105.9158.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: query cancel issues in contrib/dblink  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> 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




pgsql-hackers by date:

Previous
From: "Erik Rijkers"
Date:
Subject: Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset
Next
From: Simon Riggs
Date:
Subject: Re: pg_stop_backup does not complete