postgres-xc-committers Mailing List for Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  5c3f03ccffa86b775e1d4d9be668accebaa2e4c9 (commit)
      from  8427ea322eabca18fa21f286c2284aa4ffa105a8 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=5c3f03ccffa86b775e1d4d9be668accebaa2e4c9

commit 5c3f03ccffa86b775e1d4d9be668accebaa2e4c9
Author: Koichi Suzuki <koi...@gm...>
Date:   Fri Mar 30 09:22:18 2012 +0900

    Adds pgxc_clean utility.   pgxc_clean checks all the two phase commit status
    to find any outstanding ones, then cleans up them to keep transaction status
    consistent throughout Postgres-XC database cluster.

M	doc-xc/src/sgml/ref/allfiles.sgmlin
M	doc-xc/src/sgml/reference.sgmlin
M	src/Makefile
A	src/pgxc/bin/pgxc_clean/Makefile
A	src/pgxc/bin/pgxc_clean/pgxc_clean.c
A	src/pgxc/bin/pgxc_clean/pgxc_clean.h
A	src/pgxc/bin/pgxc_clean/pgxc_clean_test.sh
A	src/pgxc/bin/pgxc_clean/txninfo.c
A	src/pgxc/bin/pgxc_clean/txninfo.h

-----------------------------------------------------------------------

Summary of changes:
 doc-xc/src/sgml/ref/allfiles.sgmlin        |    3 +
 doc-xc/src/sgml/reference.sgmlin           |    3 +
 src/Makefile                               |    3 +-
 src/pgxc/bin/pgxc_clean/Makefile           |   46 ++
 src/pgxc/bin/pgxc_clean/pgxc_clean.c       | 1043 ++++++++++++++++++++++++++++
 src/pgxc/bin/pgxc_clean/pgxc_clean.h       |   13 +
 src/pgxc/bin/pgxc_clean/pgxc_clean_test.sh |   85 +++
 src/pgxc/bin/pgxc_clean/txninfo.c          |  338 +++++++++
 src/pgxc/bin/pgxc_clean/txninfo.h          |   83 +++
 9 files changed, 1616 insertions(+), 1 deletions(-)
 create mode 100644 src/pgxc/bin/pgxc_clean/Makefile
 create mode 100644 src/pgxc/bin/pgxc_clean/pgxc_clean.c
 create mode 100644 src/pgxc/bin/pgxc_clean/pgxc_clean.h
 create mode 100644 src/pgxc/bin/pgxc_clean/pgxc_clean_test.sh
 create mode 100644 src/pgxc/bin/pgxc_clean/txninfo.c
 create mode 100644 src/pgxc/bin/pgxc_clean/txninfo.h


hooks/post-receive
-- 
Postgres-XC

Hi Michael,
Was this patch discussed on the mailing list? I did not see any relevant
discussion.

There can a possibility that resorigtbl is set the result table but it's
not added in rewriting. In this case, would there be erroneous column
updation? Instead of resorigtbl can you use some attribute inside the Var
node like varno?

On Thu, Mar 29, 2012 at 10:01 AM, Michael Paquier <
mic...@us...> wrote:

> Project "Postgres-XC".
>
> The branch, master has been updated
>       via  8427ea322eabca18fa21f286c2284aa4ffa105a8 (commit)
>      from  0f11b36d79827bd8b2ed66a31e074e1a8a86fba3 (commit)
>
>
> - Log -----------------------------------------------------------------
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8427ea322eabca18fa21f286c2284aa4ffa105a8
>
> commit 8427ea322eabca18fa21f286c2284aa4ffa105a8
> Author: Michael P <mi...@ot...>
> Date:   Thu Mar 29 13:32:53 2012 +0900
>
>    Correct remote DELETE planning for multiple relations
>
>    In case several relations were involved in a remote DELETE (rules,
>    join, etc.), remote query was not correctly generated because it
>    took into account not only its target entries, but also the ones
>    from other relations.
>    A reference of the original table is added in target entries and
>    this is compared to the relation whose remote DELETE is generated
>    to insure that all the operations are consistent.
>
>    This had consequences like bug 3512657, but also on the usage of
>    rules on DELETE.
>
> M       src/backend/optimizer/plan/createplan.c
> M       src/backend/rewrite/rewriteHandler.c
>
> -----------------------------------------------------------------------
>
> Summary of changes:
>  src/backend/optimizer/plan/createplan.c |   13 ++++++++++---
>  src/backend/rewrite/rewriteHandler.c    |    9 +++++++++
>  2 files changed, 19 insertions(+), 3 deletions(-)
>
>
> hooks/post-receive
> --
> Postgres-XC
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Postgres-xc-committers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Project "Postgres-XC".

The branch, master has been updated
       via  8427ea322eabca18fa21f286c2284aa4ffa105a8 (commit)
      from  0f11b36d79827bd8b2ed66a31e074e1a8a86fba3 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8427ea322eabca18fa21f286c2284aa4ffa105a8

commit 8427ea322eabca18fa21f286c2284aa4ffa105a8
Author: Michael P <mi...@ot...>
Date:   Thu Mar 29 13:32:53 2012 +0900

    Correct remote DELETE planning for multiple relations
    
    In case several relations were involved in a remote DELETE (rules,
    join, etc.), remote query was not correctly generated because it
    took into account not only its target entries, but also the ones
    from other relations.
    A reference of the original table is added in target entries and
    this is compared to the relation whose remote DELETE is generated
    to insure that all the operations are consistent.
    
    This had consequences like bug 3512657, but also on the usage of
    rules on DELETE.

M	src/backend/optimizer/plan/createplan.c
M	src/backend/rewrite/rewriteHandler.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/optimizer/plan/createplan.c |   13 ++++++++++---
 src/backend/rewrite/rewriteHandler.c    |    9 +++++++++
 2 files changed, 19 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  0f11b36d79827bd8b2ed66a31e074e1a8a86fba3 (commit)
      from  0eaba1379aa2dde346a53eb15f8849c0e09861d0 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0f11b36d79827bd8b2ed66a31e074e1a8a86fba3

commit 0f11b36d79827bd8b2ed66a31e074e1a8a86fba3
Author: Koichi Suzuki <koi...@gm...>
Date:   Thu Mar 29 11:57:44 2012 +0900

    This commit extends commit/rollback prepared statement for xc_maintenance_mode = on.  With xc_maintenance_mode = on, these command will work only locally and report the result to GTM.
    
    This is needed to maintain transaction integrity after failed node is back or failover took place.

M	doc-xc/src/sgml/config.sgmlin
M	doc-xc/src/sgml/ref/commit_prepared.sgmlin
M	doc-xc/src/sgml/ref/rollback_prepared.sgmlin
M	src/backend/access/transam/twophase.c
M	src/backend/parser/analyze.c
M	src/backend/pgxc/pool/execRemote.c
M	src/backend/tcop/utility.c

-----------------------------------------------------------------------

Summary of changes:
 doc-xc/src/sgml/config.sgmlin                |   25 ++++++++++-
 doc-xc/src/sgml/ref/commit_prepared.sgmlin   |    7 +++
 doc-xc/src/sgml/ref/rollback_prepared.sgmlin |   16 +++++++
 src/backend/access/transam/twophase.c        |   45 ++++++++++++++++++--
 src/backend/parser/analyze.c                 |    5 +-
 src/backend/pgxc/pool/execRemote.c           |   59 ++++++++++++++++++-------
 src/backend/tcop/utility.c                   |    4 +-
 7 files changed, 133 insertions(+), 28 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  0eaba1379aa2dde346a53eb15f8849c0e09861d0 (commit)
      from  dfda23e7547f457e15d79054f81d30e826faeecf (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0eaba1379aa2dde346a53eb15f8849c0e09861d0

commit 0eaba1379aa2dde346a53eb15f8849c0e09861d0
Author: Koichi Suzuki <koi...@gm...>
Date:   Thu Mar 29 11:03:25 2012 +0900

    This commit adds GUC parameter xc_maintenance_mode.   This is needed to control
    behavior of some statements to be used to maintain XC database integrity by
    dedicate utility programs such as pgxc_clean, which is now under the
    development.
    
    Also, this patch modifies implicit 2PC xid to _$XC$%u where %u is the transactionId.
    Because it is essential to distinguish implicit 2PC from explicit one to maintain
    database consisitensy, this patch checks xid in PREPARE TRANSACTION and rejects
    xid for implicit 2PC.
    
    See documentation for details.

M	doc-xc/src/sgml/config.sgmlin
M	doc-xc/src/sgml/ref/prepare_transaction.sgmlin
M	src/backend/access/transam/xact.c
M	src/backend/pgxc/Makefile
A	src/backend/pgxc/xc_maintenance_mode/Makefile
A	src/backend/pgxc/xc_maintenance_mode/xc_maintenance_mode.c
M	src/backend/tcop/utility.c
M	src/backend/utils/misc/guc.c
M	src/include/access/xact.h
A	src/include/pgxc/xc_maintenance_mode.h
M	src/include/utils/guc_tables.h

-----------------------------------------------------------------------

Summary of changes:
 doc-xc/src/sgml/config.sgmlin                      |   15 ++++
 doc-xc/src/sgml/ref/prepare_transaction.sgmlin     |    6 ++
 src/backend/access/transam/xact.c                  |   14 ++++
 src/backend/pgxc/Makefile                          |    2 +-
 .../pgxc/{barrier => xc_maintenance_mode}/Makefile |    4 +-
 .../pgxc/xc_maintenance_mode/xc_maintenance_mode.c |    5 ++
 src/backend/tcop/utility.c                         |   13 ++++
 src/backend/utils/misc/guc.c                       |   74 ++++++++++++++++++++
 src/include/access/xact.h                          |    1 +
 src/include/pgxc/xc_maintenance_mode.h             |   12 +++
 src/include/utils/guc_tables.h                     |    7 ++-
 11 files changed, 149 insertions(+), 4 deletions(-)
 copy src/backend/pgxc/{barrier => xc_maintenance_mode}/Makefile (85%)
 create mode 100644 src/backend/pgxc/xc_maintenance_mode/xc_maintenance_mode.c
 create mode 100644 src/include/pgxc/xc_maintenance_mode.h


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  dfda23e7547f457e15d79054f81d30e826faeecf (commit)
      from  0b3ffcff380d0fe14cb11d6c2f4b88fe20346ff1 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=dfda23e7547f457e15d79054f81d30e826faeecf

commit dfda23e7547f457e15d79054f81d30e826faeecf
Author: Michael P <mi...@ot...>
Date:   Thu Mar 29 10:20:05 2012 +0900

    Alternative regression output for test inherit
    
    This is related to bug 3141171, where XC tries to perform joins with
    objects Oids but it fails because OIDs are not consistent among nodes
    in the cluster. This is a restriction of the XC current architecture.
    Some additional queries, using a cast on regclass with relation name
    are used to show the correct output in the test. This part of the test
    has been updated in consequence.
    
    There are still diffs in test inherit but it is not related to this
    bug, so this regression still fails.

A	src/test/regress/expected/inherit_1.out
M	src/test/regress/sql/inherit.sql

-----------------------------------------------------------------------

Summary of changes:
 .../expected/{inherit.out => inherit_1.out}        |  725 +++++++++++---------
 src/test/regress/sql/inherit.sql                   |   45 ++
 2 files changed, 462 insertions(+), 308 deletions(-)
 copy src/test/regress/expected/{inherit.out => inherit_1.out} (74%)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  0b3ffcff380d0fe14cb11d6c2f4b88fe20346ff1 (commit)
      from  1957c940883036cb30700b400356eda3755139db (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0b3ffcff380d0fe14cb11d6c2f4b88fe20346ff1

commit 0b3ffcff380d0fe14cb11d6c2f4b88fe20346ff1
Author: Michael P <mi...@ot...>
Date:   Thu Mar 29 09:46:42 2012 +0900

    GTM callback mechanism for sequence consistency on GTM
    
    Addition of a mechanism to insure that sequence information
    is kept consistent on GTM within a transaction block.
    A callback to drop sequences on GTM is registered when sequences are
    dropped or created. Then this callback is used when a transaction that created
    sequence is aborted or when a transaction that dropped a sequence commits,
    insuring that sequence information is properly rollbacked or committed on GTM.

M	src/backend/access/transam/xact.c
M	src/backend/catalog/dependency.c
M	src/backend/commands/sequence.c
M	src/include/access/xact.h
M	src/include/commands/sequence.h

-----------------------------------------------------------------------

Summary of changes:
 src/backend/access/transam/xact.c |  122 +++++++++++++++++++++++++++++++++++++
 src/backend/catalog/dependency.c  |   12 ++--
 src/backend/commands/sequence.c   |   84 +++++++++++++++++++++++++-
 src/include/access/xact.h         |   15 +++++
 src/include/commands/sequence.h   |   17 +++++
 5 files changed, 244 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  1957c940883036cb30700b400356eda3755139db (commit)
      from  9d71db236af45cda76b31a870c23482e988a8896 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=1957c940883036cb30700b400356eda3755139db

commit 1957c940883036cb30700b400356eda3755139db
Author: Ashutosh Bapat <ash...@en...>
Date:   Wed Mar 28 14:22:05 2012 +0530

    A query can not be shipped to the datanodes because of many reasons. Store these
    reasons in the FQS_context for debugging and further optimizations.

M	src/backend/pgxc/plan/planner.c
M	src/include/pgxc/planner.h

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/plan/planner.c |  189 +++++++++++++++++++++++++--------------
 src/include/pgxc/planner.h      |   24 ++++-
 2 files changed, 140 insertions(+), 73 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  9d71db236af45cda76b31a870c23482e988a8896 (commit)
      from  d16e34e9c66b1b7949991adb8b6aba172e4f5a6f (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9d71db236af45cda76b31a870c23482e988a8896

commit 9d71db236af45cda76b31a870c23482e988a8896
Author: Ashutosh Bapat <ash...@en...>
Date:   Tue Mar 27 12:09:01 2012 +0530

    Some C structures and functions were not used after the new FQS code was
    implemented. Removed those.

M	src/backend/pgxc/plan/planner.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/plan/planner.c |  198 +--------------------------------------
 1 files changed, 1 insertions(+), 197 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  d16e34e9c66b1b7949991adb8b6aba172e4f5a6f (commit)
      from  118bf9d0bfd000171fd71c37f528db5664d4eb4a (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=d16e34e9c66b1b7949991adb8b6aba172e4f5a6f

commit d16e34e9c66b1b7949991adb8b6aba172e4f5a6f
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 27 10:14:01 2012 +0530

    Honor collations while handling results at the coordinator. This fixes a part of
    collation test case failure

M	src/backend/optimizer/plan/createplan.c
M	src/backend/pgxc/pool/execRemote.c
M	src/backend/utils/sort/tuplesort.c
M	src/include/pgxc/planner.h
M	src/include/utils/tuplesort.h

-----------------------------------------------------------------------

Summary of changes:
 src/backend/optimizer/plan/createplan.c |    1 +
 src/backend/pgxc/pool/execRemote.c      |    1 +
 src/backend/utils/sort/tuplesort.c      |   22 ++++++++++++++--------
 src/include/pgxc/planner.h              |    1 +
 src/include/utils/tuplesort.h           |    2 +-
 5 files changed, 18 insertions(+), 9 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  118bf9d0bfd000171fd71c37f528db5664d4eb4a (commit)
      from  667ce0824d0bcb7acbc128d747b131d78d4ed73e (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=118bf9d0bfd000171fd71c37f528db5664d4eb4a

commit 118bf9d0bfd000171fd71c37f528db5664d4eb4a
Author: Michael P <mi...@ot...>
Date:   Tue Mar 27 11:22:31 2012 +0900

    Clean up warnings in execRemote.c
    
    Some static functions are not used anymore since transaction handling
    has been cleaned up recently.

M	src/backend/pgxc/pool/execRemote.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/pool/execRemote.c |   55 ------------------------------------
 1 files changed, 0 insertions(+), 55 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  667ce0824d0bcb7acbc128d747b131d78d4ed73e (commit)
       via  12bce7a547ec92e3c147d2c12bb5f2ba050aef29 (commit)
      from  d6c3f65ec3802dc5506531ed4870fe8fccb20661 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=667ce0824d0bcb7acbc128d747b131d78d4ed73e

commit 667ce0824d0bcb7acbc128d747b131d78d4ed73e
Merge: 12bce7a d6c3f65
Author: Koichi Suzuki <koi...@gm...>
Date:   Mon Mar 26 16:42:39 2012 +0900

    Merge branch 'master' of ssh://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc


http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=12bce7a547ec92e3c147d2c12bb5f2ba050aef29

commit 667ce0824d0bcb7acbc128d747b131d78d4ed73e
Merge: 12bce7a d6c3f65
Author: Koichi Suzuki <koi...@gm...>
Date:   Mon Mar 26 16:42:39 2012 +0900

    Merge branch 'master' of ssh://postgres-xc.git.sourceforge.net/gitroot/postgres-xc/postgres-xc


-----------------------------------------------------------------------

Summary of changes:
 doc-xc/src/sgml/func.sgmlin          |    8 ++++++++
 src/backend/access/transam/transam.c |   28 ++++++++++++++++++++++++++++
 src/include/catalog/pg_proc.h        |    2 ++
 src/include/utils/builtins.h         |    5 +++++
 4 files changed, 43 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  d6c3f65ec3802dc5506531ed4870fe8fccb20661 (commit)
      from  400958d15da435c74bd8e911bf4e3ab530618c9f (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=d6c3f65ec3802dc5506531ed4870fe8fccb20661

commit d6c3f65ec3802dc5506531ed4870fe8fccb20661
Author: Ashutosh Bapat <ash...@en...>
Date:   Mon Mar 26 12:57:43 2012 +0530

    Fix for bug 3465997. FieldStore node with more than one fields is not deparsed
    in processIndirection(). Since this is PostgreSQL code, we should get the fix
    from PostgreSQL repository, whenever that gets fixed. For the time being we do
    not "fast-query-ship" a parse tree with FieldStore node.

M	src/backend/pgxc/plan/planner.c
M	src/test/regress/sql/rowtypes.sql

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/plan/planner.c   |   13 +++++++++++--
 src/test/regress/sql/rowtypes.sql |    3 +--
 2 files changed, 12 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
Postgres-XC

On Thu, Mar 22, 2012 at 5:36 PM, Koichi Suzuki <koi...@gm...> wrote:

> Difference in conversion of floating number affects the last digits.
> Our case is caused by this (and by internal module from PostgreSQL).
>  Conversion tool place at the datanode and sent to the coordinator in
> a text format with different precision (last digit was affected by
> this).
>
>
Suzuki-san,
This is different thread. This one is related to new GUCs added for fast
query shipping. Probably you want to reply to aggregates thread :)


> Regards;
> ----------
> Koichi Suzuki
>
>
>
> 2012年3月22日19:51 Ahsan Hadi <ahs...@en...>:
> >
> >
> > On Thu, Mar 22, 2012 at 10:16 AM, Koichi Suzuki <koi...@gm...>
> > wrote:
> >>
> >> We can comment why XC changed .out file to .sql file.    Or, we can
> >> change the file name to *_xc.out to indicate that there's some change
> >> in XC for some reason.
> >
> >
> > Since this output will always be same on XC why don't we consider
> changing
> > the rangefuncs.out instead of creating alternative expected output files.
> > Creating alternative expected output files can cause a confusion or
> sometime
> > cause a bug to be pushed under the rug so it will be better to avoid
> > alternative output file as much as possible.
> >
> >>
> >> Regards;
> >> ----------
> >> Koichi Suzuki
> >>
> >>
> >>
> >> 2012年3月22日14:02 Ashutosh Bapat <ash...@en...>:
> >> >
> >> >
> >> > On Thu, Mar 22, 2012 at 10:18 AM, Michael Paquier
> >> > <mic...@gm...> wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Thu, Mar 22, 2012 at 1:42 PM, Ashutosh Bapat
> >> >> <ash...@en...> wrote:
> >> >>>
> >> >>> Hi Michael,
> >> >>> Is the only difference between rangefuncs.out and rangefuncs_1.out
> the
> >> >>> new GUCs added?
> >> >>
> >> >> Yes, there are some enable_*fqs* parameters that are exclusively XC
> >> >> related.
> >> >>
> >> >>>
> >> >>> In that case it might be better to change rangefuncs.out itself,
> >> >>> rather
> >> >>> than creating the alternate output file, since that's the expected
> >> >>> output in
> >> >>> XC.
> >> >>
> >> >> We discussed about that a long time ago and it was decided to create
> >> >> alternative output results to limit the possible interactions of our
> >> >> code
> >> >> with Postgres itself.
> >> >
> >> >
> >> > I am not sure about this conclusion. We have been changing the sql and
> >> > out
> >> > files in some cases. I think, it needs to be handled on case by case
> >> > basis.
> >> > When there is a feature blocked and the outputs differ, we should
> create
> >> > an
> >> > alternate output file. When the diff is inherent to XC, we should
> change
> >> > the
> >> > output. In this particular case, we are not going to take out those
> >> > GUCs, so
> >> > the output is going to have those GUCs there. There is not reason to
> not
> >> > change the output file. Having alternate output file creates confusion
> >> > as to
> >> > which of the outputs are correct. FAILure of a testcase with alternate
> >> > output depends upon the diff between the alternate outputs. So, we
> >> > should
> >> > avoid alternate outputs as much as well as think about the merge of
> >> > testcases and outputs. So, we need a balance in both the approaches.
> >> >
> >> >>
> >> >> --
> >> >> Michael Paquier
> >> >> http://michael.otacoo.com
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Best Wishes,
> >> > Ashutosh Bapat
> >> > EntepriseDB Corporation
> >> > The Enterprise Postgres Company
> >> >
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > This SF email is sponsosred by:
> >> > Try Windows Azure free for 90 days Click Here
> >> > http://p.sf.net/sfu/sfd2d-msazure
> >> > _______________________________________________
> >> > Postgres-xc-committers mailing list
> >> > Pos...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
> >> >
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> This SF email is sponsosred by:
> >> Try Windows Azure free for 90 days Click Here
> >> http://p.sf.net/sfu/sfd2d-msazure
> >> _______________________________________________
> >> Postgres-xc-committers mailing list
> >> Pos...@li...
> >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
> >
> >
> >
> >
> > --
> > Ahsan Hadi
> > Snr Director Product Development
> > EnterpriseDB Corporation
> > The Enterprise Postgres Company
> >
> > Phone: +92-51-8358874
> > Mobile: +92-333-5162114
> >
> > Website: www.enterprisedb.com
> > EnterpriseDB Blog: http://blogs.enterprisedb.com/
> > Follow us on Twitter: http://www.twitter.com/enterprisedb
> >
> > This e-mail message (and any attachment) is intended for the use of the
> > individual or entity to whom it is addressed. This message contains
> > information from EnterpriseDB Corporation that may be privileged,
> > confidential, or exempt from disclosure under applicable law. If you are
> not
> > the intended recipient or authorized to receive this for the intended
> > recipient, any use, dissemination, distribution, retention, archiving, or
> > copying of this communication is strictly prohibited. If you have
> received
> > this e-mail in error, please notify the sender immediately by reply
> e-mail
> > and delete this message.
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Difference in conversion of floating number affects the last digits.
Our case is caused by this (and by internal module from PostgreSQL).
 Conversion tool place at the datanode and sent to the coordinator in
a text format with different precision (last digit was affected by
this).

Regards;
----------
Koichi Suzuki



2012年3月22日19:51 Ahsan Hadi <ahs...@en...>:
>
>
> On Thu, Mar 22, 2012 at 10:16 AM, Koichi Suzuki <koi...@gm...>
> wrote:
>>
>> We can comment why XC changed .out file to .sql file.    Or, we can
>> change the file name to *_xc.out to indicate that there's some change
>> in XC for some reason.
>
>
> Since this output will always be same on XC why don't we consider changing
> the rangefuncs.out instead of creating alternative expected output files.
> Creating alternative expected output files can cause a confusion or sometime
> cause a bug to be pushed under the rug so it will be better to avoid
> alternative output file as much as possible.
>
>>
>> Regards;
>> ----------
>> Koichi Suzuki
>>
>>
>>
>> 2012年3月22日14:02 Ashutosh Bapat <ash...@en...>:
>> >
>> >
>> > On Thu, Mar 22, 2012 at 10:18 AM, Michael Paquier
>> > <mic...@gm...> wrote:
>> >>
>> >>
>> >>
>> >> On Thu, Mar 22, 2012 at 1:42 PM, Ashutosh Bapat
>> >> <ash...@en...> wrote:
>> >>>
>> >>> Hi Michael,
>> >>> Is the only difference between rangefuncs.out and rangefuncs_1.out the
>> >>> new GUCs added?
>> >>
>> >> Yes, there are some enable_*fqs* parameters that are exclusively XC
>> >> related.
>> >>
>> >>>
>> >>> In that case it might be better to change rangefuncs.out itself,
>> >>> rather
>> >>> than creating the alternate output file, since that's the expected
>> >>> output in
>> >>> XC.
>> >>
>> >> We discussed about that a long time ago and it was decided to create
>> >> alternative output results to limit the possible interactions of our
>> >> code
>> >> with Postgres itself.
>> >
>> >
>> > I am not sure about this conclusion. We have been changing the sql and
>> > out
>> > files in some cases. I think, it needs to be handled on case by case
>> > basis.
>> > When there is a feature blocked and the outputs differ, we should create
>> > an
>> > alternate output file. When the diff is inherent to XC, we should change
>> > the
>> > output. In this particular case, we are not going to take out those
>> > GUCs, so
>> > the output is going to have those GUCs there. There is not reason to not
>> > change the output file. Having alternate output file creates confusion
>> > as to
>> > which of the outputs are correct. FAILure of a testcase with alternate
>> > output depends upon the diff between the alternate outputs. So, we
>> > should
>> > avoid alternate outputs as much as well as think about the merge of
>> > testcases and outputs. So, we need a balance in both the approaches.
>> >
>> >>
>> >> --
>> >> Michael Paquier
>> >> http://michael.otacoo.com
>> >
>> >
>> >
>> >
>> > --
>> > Best Wishes,
>> > Ashutosh Bapat
>> > EntepriseDB Corporation
>> > The Enterprise Postgres Company
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > This SF email is sponsosred by:
>> > Try Windows Azure free for 90 days Click Here
>> > http://p.sf.net/sfu/sfd2d-msazure
>> > _______________________________________________
>> > Postgres-xc-committers mailing list
>> > Pos...@li...
>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> Postgres-xc-committers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>
>
>
>
> --
> Ahsan Hadi
> Snr Director Product Development
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>
> Phone: +92-51-8358874
> Mobile: +92-333-5162114
>
> Website: www.enterprisedb.com
> EnterpriseDB Blog: http://blogs.enterprisedb.com/
> Follow us on Twitter: http://www.twitter.com/enterprisedb
>
> This e-mail message (and any attachment) is intended for the use of the
> individual or entity to whom it is addressed. This message contains
> information from EnterpriseDB Corporation that may be privileged,
> confidential, or exempt from disclosure under applicable law. If you are not
> the intended recipient or authorized to receive this for the intended
> recipient, any use, dissemination, distribution, retention, archiving, or
> copying of this communication is strictly prohibited. If you have received
> this e-mail in error, please notify the sender immediately by reply e-mail
> and delete this message.

On Thu, Mar 22, 2012 at 10:16 AM, Koichi Suzuki <koi...@gm...>wrote:

> We can comment why XC changed .out file to .sql file.    Or, we can
> change the file name to *_xc.out to indicate that there's some change
> in XC for some reason.
>

Since this output will always be same on XC why don't we consider changing
the rangefuncs.out instead of creating alternative expected output files.
Creating alternative expected output files can cause a confusion or
sometime cause a bug to be pushed under the rug so it will be better to
avoid alternative output file as much as possible.


> Regards;
> ----------
> Koichi Suzuki
>
>
>
> 2012年3月22日14:02 Ashutosh Bapat <ash...@en...>:
> >
> >
> > On Thu, Mar 22, 2012 at 10:18 AM, Michael Paquier
> > <mic...@gm...> wrote:
> >>
> >>
> >>
> >> On Thu, Mar 22, 2012 at 1:42 PM, Ashutosh Bapat
> >> <ash...@en...> wrote:
> >>>
> >>> Hi Michael,
> >>> Is the only difference between rangefuncs.out and rangefuncs_1.out the
> >>> new GUCs added?
> >>
> >> Yes, there are some enable_*fqs* parameters that are exclusively XC
> >> related.
> >>
> >>>
> >>> In that case it might be better to change rangefuncs.out itself, rather
> >>> than creating the alternate output file, since that's the expected
> output in
> >>> XC.
> >>
> >> We discussed about that a long time ago and it was decided to create
> >> alternative output results to limit the possible interactions of our
> code
> >> with Postgres itself.
> >
> >
> > I am not sure about this conclusion. We have been changing the sql and
> out
> > files in some cases. I think, it needs to be handled on case by case
> basis.
> > When there is a feature blocked and the outputs differ, we should create
> an
> > alternate output file. When the diff is inherent to XC, we should change
> the
> > output. In this particular case, we are not going to take out those
> GUCs, so
> > the output is going to have those GUCs there. There is not reason to not
> > change the output file. Having alternate output file creates confusion
> as to
> > which of the outputs are correct. FAILure of a testcase with alternate
> > output depends upon the diff between the alternate outputs. So, we should
> > avoid alternate outputs as much as well as think about the merge of
> > testcases and outputs. So, we need a balance in both the approaches.
> >
> >>
> >> --
> >> Michael Paquier
> >> http://michael.otacoo.com
> >
> >
> >
> >
> > --
> > Best Wishes,
> > Ashutosh Bapat
> > EntepriseDB Corporation
> > The Enterprise Postgres Company
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF email is sponsosred by:
> > Try Windows Azure free for 90 days Click Here
> > http://p.sf.net/sfu/sfd2d-msazure
> > _______________________________________________
> > Postgres-xc-committers mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
> >
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Postgres-xc-committers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>



-- 
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.

Project "Postgres-XC".

The branch, master has been updated
       via  400958d15da435c74bd8e911bf4e3ab530618c9f (commit)
      from  ad4ea5eff4c28ea930f1ab301784d11d5550b3ed (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=400958d15da435c74bd8e911bf4e3ab530618c9f

commit 400958d15da435c74bd8e911bf4e3ab530618c9f
Author: Michael P <mi...@ot...>
Date:   Thu Mar 22 16:27:06 2012 +0900

    Fix a problem regarding obtention of distribution data
    for database relations in XC planner when checking for updates
    on distribution columns.
    
    Some relations like views have no distribution data, so only relations
    whose relkind is a table can be accessed in this case.

M	src/backend/pgxc/plan/planner.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/plan/planner.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
Postgres-XC

We can comment why XC changed .out file to .sql file.    Or, we can
change the file name to *_xc.out to indicate that there's some change
in XC for some reason.

Regards;
----------
Koichi Suzuki



2012年3月22日14:02 Ashutosh Bapat <ash...@en...>:
>
>
> On Thu, Mar 22, 2012 at 10:18 AM, Michael Paquier
> <mic...@gm...> wrote:
>>
>>
>>
>> On Thu, Mar 22, 2012 at 1:42 PM, Ashutosh Bapat
>> <ash...@en...> wrote:
>>>
>>> Hi Michael,
>>> Is the only difference between rangefuncs.out and rangefuncs_1.out the
>>> new GUCs added?
>>
>> Yes, there are some enable_*fqs* parameters that are exclusively XC
>> related.
>>
>>>
>>> In that case it might be better to change rangefuncs.out itself, rather
>>> than creating the alternate output file, since that's the expected output in
>>> XC.
>>
>> We discussed about that a long time ago and it was decided to create
>> alternative output results to limit the possible interactions of our code
>> with Postgres itself.
>
>
> I am not sure about this conclusion. We have been changing the sql and out
> files in some cases. I think, it needs to be handled on case by case basis.
> When there is a feature blocked and the outputs differ, we should create an
> alternate output file. When the diff is inherent to XC, we should change the
> output. In this particular case, we are not going to take out those GUCs, so
> the output is going to have those GUCs there. There is not reason to not
> change the output file. Having alternate output file creates confusion as to
> which of the outputs are correct. FAILure of a testcase with alternate
> output depends upon the diff between the alternate outputs. So, we should
> avoid alternate outputs as much as well as think about the merge of
> testcases and outputs. So, we need a balance in both the approaches.
>
>>
>> --
>> Michael Paquier
>> http://michael.otacoo.com
>
>
>
>
> --
> Best Wishes,
> Ashutosh Bapat
> EntepriseDB Corporation
> The Enterprise Postgres Company
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Postgres-xc-committers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>

On Thu, Mar 22, 2012 at 10:18 AM, Michael Paquier <mic...@gm...
> wrote:

>
>
> On Thu, Mar 22, 2012 at 1:42 PM, Ashutosh Bapat <
> ash...@en...> wrote:
>
>> Hi Michael,
>> Is the only difference between rangefuncs.out and rangefuncs_1.out the
>> new GUCs added?
>>
> Yes, there are some enable_*fqs* parameters that are exclusively XC
> related.
>
>
>> In that case it might be better to change rangefuncs.out itself, rather
>> than creating the alternate output file, since that's the expected output
>> in XC.
>>
> We discussed about that a long time ago and it was decided to create
> alternative output results to limit the possible interactions of our code
> with Postgres itself.
>

I am not sure about this conclusion. We have been changing the sql and out
files in some cases. I think, it needs to be handled on case by case basis.
When there is a feature blocked and the outputs differ, we should create an
alternate output file. When the diff is inherent to XC, we should change
the output. In this particular case, we are not going to take out those
GUCs, so the output is going to have those GUCs there. There is not reason
to not change the output file. Having alternate output file creates
confusion as to which of the outputs are correct. FAILure of a testcase
with alternate output depends upon the diff between the alternate outputs.
So, we should avoid alternate outputs as much as well as think about the
merge of testcases and outputs. So, we need a balance in both the
approaches.


> --
> Michael Paquier
> http://michael.otacoo.com
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Hi Michael,
Is the only difference between rangefuncs.out and rangefuncs_1.out the new
GUCs added? In that case it might be better to change rangefuncs.out
itself, rather than creating the alternate output file, since that's the
expected output in XC.

On Thu, Mar 22, 2012 at 8:32 AM, Michael Paquier <
mic...@us...> wrote:

> Project "Postgres-XC".
>
> The branch, master has been updated
>       via  ad4ea5eff4c28ea930f1ab301784d11d5550b3ed (commit)
>      from  6086e355914fdebcd2c002d7ee1d3132582a33f9 (commit)
>
>
> - Log -----------------------------------------------------------------
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=ad4ea5eff4c28ea930f1ab301784d11d5550b3ed
>
> commit ad4ea5eff4c28ea930f1ab301784d11d5550b3ed
> Author: Michael P <mi...@ot...>
> Date:   Thu Mar 22 12:05:50 2012 +0900
>
>    Fix for regression test rangefuncs
>
>    Some parameters have been added to pg_settings for FQS.
>
> A       src/test/regress/expected/rangefuncs_1.out
>
> -----------------------------------------------------------------------
>
> Summary of changes:
>  .../expected/{rangefuncs.out => rangefuncs_1.out}  |   39
> +++++++++-----------
>  1 files changed, 18 insertions(+), 21 deletions(-)
>  copy src/test/regress/expected/{rangefuncs.out => rangefuncs_1.out} (97%)
>
>
> hooks/post-receive
> --
> Postgres-XC
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Postgres-xc-committers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>



-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

Project "Postgres-XC".

The branch, master has been updated
       via  ad4ea5eff4c28ea930f1ab301784d11d5550b3ed (commit)
      from  6086e355914fdebcd2c002d7ee1d3132582a33f9 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=ad4ea5eff4c28ea930f1ab301784d11d5550b3ed

commit ad4ea5eff4c28ea930f1ab301784d11d5550b3ed
Author: Michael P <mi...@ot...>
Date:   Thu Mar 22 12:05:50 2012 +0900

    Fix for regression test rangefuncs
    
    Some parameters have been added to pg_settings for FQS.

A	src/test/regress/expected/rangefuncs_1.out

-----------------------------------------------------------------------

Summary of changes:
 .../expected/{rangefuncs.out => rangefuncs_1.out}  |   39 +++++++++-----------
 1 files changed, 18 insertions(+), 21 deletions(-)
 copy src/test/regress/expected/{rangefuncs.out => rangefuncs_1.out} (97%)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  6086e355914fdebcd2c002d7ee1d3132582a33f9 (commit)
      from  648eede9a64745eba401a9b73a747b893cf781b3 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=6086e355914fdebcd2c002d7ee1d3132582a33f9

commit 6086e355914fdebcd2c002d7ee1d3132582a33f9
Author: Michael P <mi...@ot...>
Date:   Fri Mar 16 09:38:19 2012 +0900

    Addition of initgtm: module for GTm/Proxy initialization
    
    inigtm uses the infrastructure of initdb to provide the means to
    initialize the data folder of a GTM or a GTM proxy. This is particularly
    useful in case Postgres-XC binaries are installed in a folder where a user
    cannot have access to it as, like initdb, it copies the sample configuration
    files and makes them available for GTM instances.
    
    initgtm has really a basic infrastructure now, but can be easily extended
    to provide support for a cluster ID or settings related to GTM that need
    to be decided at initialization.
    
    Documentation is included.

M	doc-xc/src/sgml/bookindex.sgmlin
M	doc-xc/src/sgml/ref/allfiles.sgmlin
A	doc-xc/src/sgml/ref/initgtm.sgmlin
M	doc-xc/src/sgml/reference.sgmlin
M	src/bin/Makefile
A	src/bin/initgtm/Makefile
A	src/bin/initgtm/initgtm.c

-----------------------------------------------------------------------

Summary of changes:
 doc-xc/src/sgml/bookindex.sgmlin     |    8 +
 doc-xc/src/sgml/ref/allfiles.sgmlin  |    3 +
 doc-xc/src/sgml/ref/initgtm.sgmlin   |  205 +++++++
 doc-xc/src/sgml/reference.sgmlin     |    3 +
 src/bin/Makefile                     |    2 +-
 src/bin/{initdb => initgtm}/Makefile |   29 +-
 src/bin/initgtm/initgtm.c            | 1117 ++++++++++++++++++++++++++++++++++
 7 files changed, 1348 insertions(+), 19 deletions(-)
 create mode 100644 doc-xc/src/sgml/ref/initgtm.sgmlin
 copy src/bin/{initdb => initgtm}/Makefile (51%)
 create mode 100644 src/bin/initgtm/initgtm.c


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  648eede9a64745eba401a9b73a747b893cf781b3 (commit)
      from  56acf9583fc7e236ad5e64c15792124f9e2411b9 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=648eede9a64745eba401a9b73a747b893cf781b3

commit 648eede9a64745eba401a9b73a747b893cf781b3
Author: Pavan Deolasee <pav...@gm...>
Date:   Thu Mar 15 12:04:08 2012 +0530

    Rearrange the commit processing so that the local transaction is prepared first
    (if required), then local pre commit processing is done which also includes
    closing any open portals and then finally commit the transaction on the remote
    nodes. This should fix some of the portal related issues that we were seeing

M	src/backend/access/transam/xact.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/access/transam/xact.c |   75 +++++++++++++++++++-----------------
 1 files changed, 40 insertions(+), 35 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  56acf9583fc7e236ad5e64c15792124f9e2411b9 (commit)
      from  f7575c1f62ae424ecfff5af1fb2bc6d6306d8300 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=56acf9583fc7e236ad5e64c15792124f9e2411b9

commit 56acf9583fc7e236ad5e64c15792124f9e2411b9
Author: Pavan Deolasee <pav...@gm...>
Date:   Wed Mar 14 14:12:19 2012 +0530

    Fix a case where we were sending ROLLBACK PREPARED command even though the
    transaction is not involved in a 2PC. This was happening especially when
    a COMMIT was failing

M	src/backend/pgxc/pool/execRemote.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/pool/execRemote.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  f7575c1f62ae424ecfff5af1fb2bc6d6306d8300 (commit)
      from  2cb1534660181954461db63425fe9534327b0bc3 (commit)


- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=f7575c1f62ae424ecfff5af1fb2bc6d6306d8300

commit f7575c1f62ae424ecfff5af1fb2bc6d6306d8300
Author: Ashutosh Bapat <ash...@en...>
Date:   Wed Mar 14 16:45:41 2012 +0900

    Enable usage of FQS planner when bound parameters and cursor options are
    provided.

M	src/backend/pgxc/plan/planner.c

-----------------------------------------------------------------------

Summary of changes:
 src/backend/pgxc/plan/planner.c |   55 ++++++++++++++++++++++++---------------
 1 files changed, 34 insertions(+), 21 deletions(-)


hooks/post-receive
-- 
Postgres-XC