postgres-xc-developers Mailing List for Postgres-XC

Hi all,

Here is a fix for bug 3389327 regarding query aliases using "from" in their
aliases.
XC planner is creating some conflicts when rebuilding queries using ORDER
BY.

This solves the diffs of regression test date.
Regards,
-- 
Michael Paquier
http://michael.otacoo.com

 I don't have anything in mind yet.
But I will look at it.
--
Michael Paquier
http://michael.otacoo.com

This mechanism was added to get prepared transaction list from the nodes and
has a few side effects. I remember taking a look at the failure in our last
F2F meeting, but then we decided to take a look at it later on. Probably we
should look at the reason of the failure if you agree that principally we
are using correct mechanism.
Do you have any suggestion for an alternate mechanism to get the prepared
transactions?

On Wed, Aug 10, 2011 at 5:40 AM, Michael Paquier
<mic...@gm...>wrote:

> Hi all,
>
> Shouldn't we remove the stuff related to pgxc_coordinator_schema that has
> been created for the regression test prepared_xacts?
> This has been initially created to be able to get prepared transaction list
> from all the nodes to pass the associated regression test, but I still get
> diffs related to that.
> There is also another thing I am not so much a fan with this configuration:
> when connecting to a database for the first time, doing an \d makes appear
> this:
> template1=# \d
>                          List of relations
>            Schema            |       Name        | Type  |  Owner
> -----------------------------+-------------------+-------+---------
>  __pgxc_coordinator_schema__ | pg_prepared_xacts | table | michael
> (1 row)
>
> While it should output this:
> template1=# \d
> No relations found.
>
> This is particularly annoying for users I think, and makes XC inconsistent
> with Postgres.
> Thoughts?
> --
> Michael Paquier
> http://michael.otacoo.com
>
>
> ------------------------------------------------------------------------------
> uberSVN's rich system and user administration capabilities and model
> configuration take the hassle out of deploying and managing Subversion and
> the tools developers use with it. Learn more about uberSVN and get a free
> download at:  http://p.sf.net/sfu/wandisco-dev2dev
>
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
>

Hi all,

Shouldn't we remove the stuff related to pgxc_coordinator_schema that has
been created for the regression test prepared_xacts?
This has been initially created to be able to get prepared transaction list
from all the nodes to pass the associated regression test, but I still get
diffs related to that.
There is also another thing I am not so much a fan with this configuration:
when connecting to a database for the first time, doing an \d makes appear
this:
template1=# \d
                         List of relations
           Schema            |       Name        | Type  |  Owner
-----------------------------+-------------------+-------+---------
 __pgxc_coordinator_schema__ | pg_prepared_xacts | table | michael
(1 row)

While it should output this:
template1=# \d
No relations found.

This is particularly annoying for users I think, and makes XC inconsistent
with Postgres.
Thoughts?
-- 
Michael Paquier
http://michael.otacoo.com