Re: Transactions involving multiple postgres foreign servers - Mailing list pgsql-hackers

From vinayak
Subject Re: Transactions involving multiple postgres foreign servers
Date
Msg-id addd9075-402f-4af5-777d-1288c75758b0@lab.ntt.co.jp
Whole thread Raw
In response to Re: Transactions involving multiple postgres foreign servers  (vinayak <Pokale_Vinayak_q3@lab.ntt.co.jp>)
List pgsql-hackers

On 2016/09/07 10:54, vinayak wrote:

Thanks for the clarification. I had added pg_fdw_xact_resolver() to resolve any transactions which can not be resolved immediately after they were prepared. There was a comment from Kevin (IIRC) that leaving transactions unresolved on the foreign server keeps the resources locked on those servers. That's not a very good situation. And nobody but the initiating server can resolve those. That functionality is important to make it a complete 2PC solution. So, please consider it to be included in your first set of patches.
The attached patch included pg_fdw_xact_resolver.

The attached patch includes the documentation.

Regards,
Vinayak Pokale
NTT Open Source Software Center
Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: pgbench - allow to store select results into variables
Next
From: Etsuro Fujita
Date:
Subject: Re: Push down more full joins in postgres_fdw