|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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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.
NTT Open Source Software Center
|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|