Re: [Postgres-xc-developers] Random failures in the regression test.

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

Only one thing is that we need to disable implicit 2PC
(enforce_two_phase_commit) to use temporary object.   It's okay within
regression test but may not be okay in more realistic schemes.

In XC case, applications do not issue 2PC statement but coordinator
will do this when a transaction is involved by more than one node
(implicit 2PC).

Temporary object cannot survive across the session.   This is the
reason why temporary object is not allowed with 2PC.   Because
implicit 2PC does not survive across sessions, I believe XC can
support this.

We should continue to discuss the other issues.

Regards;
---
Koichi Suzuki


2014-02-14 14:45 GMT+09:00 Michael Paquier <mic...@gm...>:
> On Fri, Feb 14, 2014 at 11:07 AM, Koichi Suzuki <koi...@gm...> wrote:
>> Disconnecting the connection as you suggested will bring another
>> problem such as TEMPORARY object in the subsequent queries.   We do
>> not support TEMPORARY object but I believe we should be consistent on
>> this for future releases.
> AFAIK, temporary object are supported, no? There is even a parameter
> allowing to enforce autocommit instead of 2PC when temp objects are
> used. This is dangerous, OK, but that's a trade-off and user is
> normally aware of that when using temp tables. Actually, temporary
> tables are useful even without 2PC with for example a join pushed down
> to a unique remote node: it might be better to use a temporary table
> gathering a list of keys instead of a heavy ANY clause or a array with
> many values.
> --
> Michael