Re: Transactions involving multiple postgres foreign servers

From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Vinayak Pokale <vinpokale(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Subject: Re: Transactions involving multiple postgres foreign servers
Date: 2016-09-26 07:29:30
Message-ID: addd9075-402f-4af5-777d-1288c75758b0@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: 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 Content-Type Size
0001-Support-transaction-with-foreign-servers.patch application/x-download 103.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2016-09-26 07:30:22 Re: Push down more full joins in postgres_fdw
Previous Message Amit Langote 2016-09-26 07:12:08 Re: pgbench - allow to store select results into variables