postgres-xc-committers Mailing List for Postgres-XC (Page 85)

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

Project "Postgres-XC".

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


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

commit 2cb1534660181954461db63425fe9534327b0bc3
Author: Michael P <mic...@us...>
Date:   Wed Mar 14 11:18:53 2012 +0900

    Correct doc of initdb

M	doc-xc/src/sgml/ref/initdb.sgmlin

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

Summary of changes:
 doc-xc/src/sgml/ref/initdb.sgmlin |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  ecb9d940641005d2d3672a55dc27178b62498168 (commit)
      from  203ab8bff5687ab90676faf5790fdd48c662a219 (commit)


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

commit ecb9d940641005d2d3672a55dc27178b62498168
Author: Abbas <abb...@en...>
Date:   Wed Mar 14 05:46:58 2012 +0500

    Remove execNodes member of Query structure that is not used any more

M	src/include/nodes/parsenodes.h

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

Summary of changes:
 src/include/nodes/parsenodes.h |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  203ab8bff5687ab90676faf5790fdd48c662a219 (commit)
      from  4b77b99ea9f6ec572961898bdc5440eea3c9fcbe (commit)


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

commit 203ab8bff5687ab90676faf5790fdd48c662a219
Author: Ashutosh Bapat <ash...@en...>
Date:   Tue Mar 13 10:03:20 2012 +0900

    With the new FQS code in place, we don't create children plans under RemoteQuery
    node. Thus RemoteQuery node is the leaf node in the plan. Hence children
    handling in RemoteQuery plans is not required.

M	src/backend/executor/execTuples.c
M	src/backend/pgxc/pool/execRemote.c
M	src/include/executor/tuptable.h

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

Summary of changes:
 src/backend/executor/execTuples.c  |    8 +-
 src/backend/pgxc/pool/execRemote.c |  221 +++++-------------------------------
 src/include/executor/tuptable.h    |    2 -
 3 files changed, 30 insertions(+), 201 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  4b77b99ea9f6ec572961898bdc5440eea3c9fcbe (commit)
      from  227e1bbc61c40cf72de1f7967d1ba69fe228cba7 (commit)


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

commit 4b77b99ea9f6ec572961898bdc5440eea3c9fcbe
Author: Ashutosh Bapat <ash...@en...>
Date:   Fri Mar 9 13:50:58 2012 +0530

    With the Fast Query Shipping support, a lot of functions and members of various
    structures became dead. Removed this dead code.

M	src/backend/nodes/copyfuncs.c
M	src/backend/nodes/outfuncs.c
M	src/backend/optimizer/plan/createplan.c
M	src/backend/parser/analyze.c
M	src/backend/pgxc/plan/planner.c
M	src/backend/pgxc/pool/execRemote.c
M	src/include/nodes/nodes.h
M	src/include/pgxc/locator.h
M	src/include/pgxc/planner.h

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

Summary of changes:
 src/backend/nodes/copyfuncs.c           |   25 -
 src/backend/nodes/outfuncs.c            |    3 -
 src/backend/optimizer/plan/createplan.c |    8 -
 src/backend/parser/analyze.c            |    3 -
 src/backend/pgxc/plan/planner.c         | 2646 +------------------------------
 src/backend/pgxc/pool/execRemote.c      |   44 -
 src/include/nodes/nodes.h               |    1 -
 src/include/pgxc/locator.h              |   12 -
 src/include/pgxc/planner.h              |   12 -
 9 files changed, 37 insertions(+), 2717 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  227e1bbc61c40cf72de1f7967d1ba69fe228cba7 (commit)
      from  d60329339b0c8893d9f598d927435065af528794 (commit)


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

commit 227e1bbc61c40cf72de1f7967d1ba69fe228cba7
Author: Amit Khandekar <ami...@en...>
Date:   Fri Mar 9 10:59:27 2012 +0530

    Fix for bug ID 3500214 : Plancache revalidation does not work correctly on datanodes

M	src/backend/commands/prepare.c
M	src/backend/executor/spi.c
M	src/backend/utils/cache/plancache.c
M	src/include/utils/plancache.h
M	src/test/regress/expected/plancache.out
M	src/test/regress/sql/plancache.sql

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

Summary of changes:
 src/backend/commands/prepare.c          |   41 ++++------------
 src/backend/executor/spi.c              |    3 +-
 src/backend/utils/cache/plancache.c     |   82 ++++++++++++++++++++++---------
 src/include/utils/plancache.h           |    4 +-
 src/test/regress/expected/plancache.out |    2 +-
 src/test/regress/sql/plancache.sql      |    2 +-
 6 files changed, 76 insertions(+), 58 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  36d40e8b5dd844c99af25a053f6540f36ebd82db (commit)
      from  b3f877f80a81eab00444d21887fc5a25d3ea2876 (commit)


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

commit 36d40e8b5dd844c99af25a053f6540f36ebd82db
Author: Michael P <mic...@us...>
Date:   Fri Mar 9 11:30:02 2012 +0900

    Switch node definition information to shared memory in pooler
    
    This removes dependency of pooler process with catalog table cache.
    Shared memory on pooler is organized now as follows:
    - PoolerMemoryContext (well an existing one), allocated in TopMemoryContext
    and used by the pooler process
    - PoolerCoreContext, allocated in PoolerMemoryContext, used by database pool
    contexts.
    - PoolerAgentContext, pooler agent context and used by pooler agents.
    
    The pooler agent now uses node Oids instead of node indexes. This
    protects pooler agents in case of node reordering after catalog tables
    being modified due to node DDL. The warning/error message which was thrown
    back to client connection from server if connection information was
    inconsistent is also removed thanks to that.
    
    Two new GUC parameters are used to define the maximum number of
    Coordinators and Datanodes on Coordinator respectively called
    max_coordinators and max_datanodes. This represents the maximum
    number of nodes that can be defined in cluster, and does not influence
    the dynamic behavior of cluster.
    A node definition slot in shared memory takes approximately 140 bytes.
    
    Patch by Andrei Martsinchyk.
    Review, some fix issues (preferred/primary support...) and some workarounds
    by me. Performance has been checked by Sutou Takayuki.

M	doc-xc/src/sgml/config.sgmlin
M	doc-xc/src/sgml/installation.sgmlin
M	doc-xc/src/sgml/runtime.sgmlin
M	src/backend/catalog/heap.c
M	src/backend/pgxc/nodemgr/nodemgr.c
M	src/backend/pgxc/pool/pgxcnode.c
M	src/backend/pgxc/pool/poolmgr.c
M	src/backend/pgxc/pool/poolutils.c
M	src/backend/storage/ipc/ipci.c
M	src/backend/tcop/postgres.c
M	src/backend/utils/adt/dbsize.c
M	src/backend/utils/adt/lockfuncs.c
M	src/backend/utils/misc/guc.c
M	src/backend/utils/misc/postgresql.conf.sample
M	src/include/pgxc/nodemgr.h
M	src/include/pgxc/poolmgr.h
M	src/include/storage/lwlock.h

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

Summary of changes:
 doc-xc/src/sgml/config.sgmlin                 |   24 +
 doc-xc/src/sgml/installation.sgmlin           |   24 +
 doc-xc/src/sgml/runtime.sgmlin                |   32 +-
 src/backend/catalog/heap.c                    |   42 +-
 src/backend/pgxc/nodemgr/nodemgr.c            |  281 ++++++--
 src/backend/pgxc/pool/pgxcnode.c              |   42 +-
 src/backend/pgxc/pool/poolmgr.c               | 1083 +++++++++----------------
 src/backend/pgxc/pool/poolutils.c             |   16 +-
 src/backend/storage/ipc/ipci.c                |   12 +
 src/backend/tcop/postgres.c                   |   20 -
 src/backend/utils/adt/dbsize.c                |    4 +-
 src/backend/utils/adt/lockfuncs.c             |    2 +-
 src/backend/utils/misc/guc.c                  |   27 +-
 src/backend/utils/misc/postgresql.conf.sample |    8 +-
 src/include/pgxc/nodemgr.h                    |   30 +-
 src/include/pgxc/poolmgr.h                    |   31 +-
 src/include/storage/lwlock.h                  |    1 +
 17 files changed, 805 insertions(+), 874 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  b3f877f80a81eab00444d21887fc5a25d3ea2876 (commit)
      from  6c5f56a5fe2999fb50a39cf4c049864d64aaf0e9 (commit)


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

commit b3f877f80a81eab00444d21887fc5a25d3ea2876
Author: Michael P <mi...@ot...>
Date:   Fri Mar 9 08:30:22 2012 +0900

    Update error message related to non-existent 2PC transaction
    
    Message is made consistent with PostgreSQL for a 2PC whose information
    does not exist on GTM.

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  6c5f56a5fe2999fb50a39cf4c049864d64aaf0e9 (commit)
      from  e05007f32898e5d3ab021ba6ed3da600e4449727 (commit)


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

commit 6c5f56a5fe2999fb50a39cf4c049864d64aaf0e9
Author: Pavan Deolasee <pav...@gm...>
Date:   Thu Mar 8 17:15:25 2012 +0530

    Use actual relation statistics for tables that are not distributed on
    data nodes. This shows siginificant improvement for catalog table queries
    involving joins. Earlier, all such joins were planned as nested-loop, but
    now the best plan is used.

M	src/backend/optimizer/util/plancat.c
M	src/backend/optimizer/util/relnode.c

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

Summary of changes:
 src/backend/optimizer/util/plancat.c |   28 +++++++++++++++++++++++++++-
 src/backend/optimizer/util/relnode.c |   20 --------------------
 2 files changed, 27 insertions(+), 21 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  e05007f32898e5d3ab021ba6ed3da600e4449727 (commit)
      from  ff796ab0cfb5050a3d92dc261b66bb35a03647de (commit)


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

commit e05007f32898e5d3ab021ba6ed3da600e4449727
Author: Michael P <mi...@ot...>
Date:   Thu Mar 8 11:15:56 2012 +0900

    Fox for regression test functional_deps_1
    
    Only one query was failing here but it does not fail anymore
    since FQS commit. Result is in accordance with vanilla.

M	src/test/regress/expected/functional_deps_1.out

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

Summary of changes:
 src/test/regress/expected/functional_deps_1.out |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  ff796ab0cfb5050a3d92dc261b66bb35a03647de (commit)
      from  3e17e9eb5ba0d115a385bf53d2160bb03e15001f (commit)


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

commit ff796ab0cfb5050a3d92dc261b66bb35a03647de
Author: Michael P <mi...@ot...>
Date:   Thu Mar 8 10:57:39 2012 +0900

    Fix for regression test xc_temp
    
    Since fast-query shipping is committed, FULL JOIN is correctly supported.
    It has also been checked that OUTER JOIN worked correctly in accordance with
    PostgreSQL results.

M	src/test/regress/expected/xc_temp.out

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

Summary of changes:
 src/test/regress/expected/xc_temp.out |  160 +++++++++++++++++++++++++--------
 1 files changed, 124 insertions(+), 36 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  3e17e9eb5ba0d115a385bf53d2160bb03e15001f (commit)
      from  fceab33309fbbfd0c9a6bb533f823a60d60b7e16 (commit)


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

commit 3e17e9eb5ba0d115a385bf53d2160bb03e15001f
Author: Michael P <mi...@ot...>
Date:   Thu Mar 8 10:48:54 2012 +0900

    Fix for regression test select
    
    An ORDER BY clause is missing is the last SQL of test.
    This is necessary to insure result consistency in cluster.
    It is important to notice that select.out and select_1.out have very
    close outputs.

M	src/test/regress/expected/select_1.out

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

Summary of changes:
 src/test/regress/expected/select_1.out |   68 ++++++++------------------------
 1 files changed, 17 insertions(+), 51 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  fceab33309fbbfd0c9a6bb533f823a60d60b7e16 (commit)
      from  efee9222b58c4628a620f88aa5679f5823fc8dda (commit)


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

commit fceab33309fbbfd0c9a6bb533f823a60d60b7e16
Author: Michael P <mi...@ot...>
Date:   Thu Mar 8 09:15:01 2012 +0900

    Fix code alignement issue with pg_dump
    
    This issue was perhaps due to merge with postgres 9.1.
    
    Patch by Andrei Andrei Martsinchyk

M	src/bin/pg_dump/pg_dump.c

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

Summary of changes:
 src/bin/pg_dump/pg_dump.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
Postgres-XC

Project "Postgres-XC".

The branch, master has been updated
       via  efee9222b58c4628a620f88aa5679f5823fc8dda (commit)
      from  0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb (commit)


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

commit efee9222b58c4628a620f88aa5679f5823fc8dda
Author: Ashutosh Bapat <ash...@en...>
Date:   Wed Mar 7 12:09:43 2012 +0530

    In create_remotequery_plan() there is a path in which an uninitialised variable
    distcol_expr can be used and thus can cause server crash in case its default
    value is NON-NULL. Initialised it to NULL.

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

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

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


hooks/post-receive
-- 
Postgres-XC

Hi All,

This commit message looks a bit weird.

I merged from another branch which had 6-7 commits. The commit IDs are
reflected correctly in the message, but the last commit message is
replicated. Not sure what to blame. The git log shows different log message
for every commit though.

Let me know if you see any issue with the repository.

Thanks,
Pavan

On Tue, Mar 6, 2012 at 6:43 PM, Pavan Deolasee <
pa...@us...> wrote:

> Project "Postgres-XC".
>
> The branch, master has been updated
>       via  0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb (commit)
>       via  f5c981669460bcd696a266c9a336798b29769148 (commit)
>       via  8efdf2b44e1cd42f255330abb1388a11fa0cec49 (commit)
>       via  30dc60778733551b30c74344532152be6bab675f (commit)
>       via  9f63e43eae0e69554fafd5b9032c662cf9ae120b (commit)
>       via  8b7444f3c88104d0f078fd49514bc692d95ffed0 (commit)
>       via  c547574f4ba05ae21958b5a32b4742c84ce448c9 (commit)
>       via  57e659829550d3e4c4dd82c7fef5cd3f20e94a48 (commit)
>       via  9bf0a59a76844e4e673c871790e9e49375b27eb2 (commit)
>       via  738e13b7a7945da99f06ad913a4fe570f3337abc (commit)
>      from  e1d299020b4f8cb04d11bb5f51bd86871e3e8881 (commit)
>
>
> - Log -----------------------------------------------------------------
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=f5c981669460bcd696a266c9a336798b29769148
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8efdf2b44e1cd42f255330abb1388a11fa0cec49
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=30dc60778733551b30c74344532152be6bab675f
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9f63e43eae0e69554fafd5b9032c662cf9ae120b
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8b7444f3c88104d0f078fd49514bc692d95ffed0
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=c547574f4ba05ae21958b5a32b4742c84ce448c9
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=57e659829550d3e4c4dd82c7fef5cd3f20e94a48
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9bf0a59a76844e4e673c871790e9e49375b27eb2
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=738e13b7a7945da99f06ad913a4fe570f3337abc
>
> commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
> Author: Pavan Deolasee <pav...@gm...>
> Date:   Tue Mar 6 18:38:30 2012 +0530
>
>    Remove an assertion that checks for calling AbortTransaction on an
> already
>    aborted transaction. We have seen this happening when a ROLLBACK
> statement
>    is canceled by the client. We believe this is a PostgreSQL issue, but
> gets
>    manifested by XC. We should discuss this further on the hackers list
>
> M       src/backend/storage/ipc/procarray.c
>
> -----------------------------------------------------------------------
>
> Summary of changes:
>  src/backend/access/transam/varsup.c     |   20 -
>  src/backend/access/transam/xact.c       |  806 ++++------
>  src/backend/commands/variable.c         |   14 +
>  src/backend/nodes/outfuncs.c            |    4 -
>  src/backend/optimizer/plan/createplan.c |    7 +
>  src/backend/pgxc/pool/execRemote.c      | 2543
> +++++++++++++++----------------
>  src/backend/pgxc/pool/pgxcnode.c        |  309 +----
>  src/backend/pgxc/pool/poolutils.c       |    2 +-
>  src/backend/storage/ipc/ipci.c          |    6 -
>  src/backend/storage/ipc/procarray.c     |  164 +--
>  src/backend/storage/lmgr/proc.c         |   11 +-
>  src/backend/tcop/postgres.c             |    8 -
>  src/backend/tcop/utility.c              |   95 +-
>  src/backend/utils/error/elog.c          |   15 -
>  src/backend/utils/mmgr/portalmem.c      |   11 +-
>  src/include/access/xact.h               |   17 +-
>  src/include/gtm/gtm_client.h            |    3 +-
>  src/include/pgxc/execRemote.h           |   16 +-
>  src/include/storage/lwlock.h            |    1 -
>  src/include/storage/procarray.h         |    4 -
>  20 files changed, 1715 insertions(+), 2341 deletions(-)
>
>
> hooks/post-receive
> --
> Postgres-XC
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Postgres-xc-committers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers
>



-- 
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

Project "Postgres-XC".

The branch, master has been updated
       via  0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb (commit)
       via  f5c981669460bcd696a266c9a336798b29769148 (commit)
       via  8efdf2b44e1cd42f255330abb1388a11fa0cec49 (commit)
       via  30dc60778733551b30c74344532152be6bab675f (commit)
       via  9f63e43eae0e69554fafd5b9032c662cf9ae120b (commit)
       via  8b7444f3c88104d0f078fd49514bc692d95ffed0 (commit)
       via  c547574f4ba05ae21958b5a32b4742c84ce448c9 (commit)
       via  57e659829550d3e4c4dd82c7fef5cd3f20e94a48 (commit)
       via  9bf0a59a76844e4e673c871790e9e49375b27eb2 (commit)
       via  738e13b7a7945da99f06ad913a4fe570f3337abc (commit)
      from  e1d299020b4f8cb04d11bb5f51bd86871e3e8881 (commit)


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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb
Author: Pavan Deolasee <pav...@gm...>
Date:   Tue Mar 6 18:38:30 2012 +0530

    Remove an assertion that checks for calling AbortTransaction on an already
    aborted transaction. We have seen this happening when a ROLLBACK statement
    is canceled by the client. We believe this is a PostgreSQL issue, but gets
    manifested by XC. We should discuss this further on the hackers list

M	src/backend/storage/ipc/procarray.c

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

Summary of changes:
 src/backend/access/transam/varsup.c     |   20 -
 src/backend/access/transam/xact.c       |  806 ++++------
 src/backend/commands/variable.c         |   14 +
 src/backend/nodes/outfuncs.c            |    4 -
 src/backend/optimizer/plan/createplan.c |    7 +
 src/backend/pgxc/pool/execRemote.c      | 2543 +++++++++++++++----------------
 src/backend/pgxc/pool/pgxcnode.c        |  309 +----
 src/backend/pgxc/pool/poolutils.c       |    2 +-
 src/backend/storage/ipc/ipci.c          |    6 -
 src/backend/storage/ipc/procarray.c     |  164 +--
 src/backend/storage/lmgr/proc.c         |   11 +-
 src/backend/tcop/postgres.c             |    8 -
 src/backend/tcop/utility.c              |   95 +-
 src/backend/utils/error/elog.c          |   15 -
 src/backend/utils/mmgr/portalmem.c      |   11 +-
 src/include/access/xact.h               |   17 +-
 src/include/gtm/gtm_client.h            |    3 +-
 src/include/pgxc/execRemote.h           |   16 +-
 src/include/storage/lwlock.h            |    1 -
 src/include/storage/procarray.h         |    4 -
 20 files changed, 1715 insertions(+), 2341 deletions(-)


hooks/post-receive
-- 
Postgres-XC