Re: [Postgres-xc-developers] In XC, SQL functions cannot contain utility statements

[Koichi S. <koi...@gm...>]

When you turn off enforce_two_phase_commit to off, you should be
careful that if a transactions is involved with  one node (coordinator
and/or datanode), commit is not associated with prepare transaction
and you may need manual database recovery if one of the commits fails.

We're using this in the regression test mainly to maintain temporary
object usage.    We can distinguish such implicit 2PC from explicit
ones so we may be able to enable TEMP objects in such case in 1.3 or
later.

Regards;
---
Koichi Suzuki


2014-02-04 David E. Wheeler <DA...@ju...>:
> On Feb 3, 2014, at 6:20 AM, Koichi Suzuki <koi...@gm...> wrote:
>
>> Good news.   Then this restriction can be resolved in XC-1.3.
>
> Meanwhile, it looks like I can work around it by sticking this in the functions that create or drop temporary objects in EXECUTE statements:
>
>       SET LOCAL enforce_two_phase_commit = off;
>
> Now, if only SAVEPOINTS were supported (we use a lot of exception-handling in functions), we would be set! Is SAVEPOINT support on the road map? I only see it mentioned as unsupported.
>
> https://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=Roadmap
>
> Thanks,
>
> David
>