postgres-xc-general Mailing List for Postgres-XC (Page 2)

Hi, 

I just finished the multi-master configuration of Postgres XC on my
test environment (three virtual machines):  

* VM1 - with GTM only
* VM2,
VM2 - two masters with one data-node and one coordinator on each machine


I tried to create some databases on each master to check if everything
works ok, but I found a strange issue with one database that had been
created only on one of the masters (while other databases I created and
deleted afterwards were ok): 

postgres=# l
 List of databases
 Name |
Owner | Encoding | Collate | Ctype | Access privileges

-----------+----------+----------+-------------+-------------+-----------------------

postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | 
 template0 |
postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
 | | | | |
postgres=CTc/postgres
 template1 | postgres | UTF8 | en_US.UTF-8 |
en_US.UTF-8 | =c/postgres +
 | | | | | postgres=CTc/postgres
 test2 |
postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | 
 whatnot | postgres | UTF8 |
en_US.UTF-8 | en_US.UTF-8 |  

vs 

postgres=# l
 List of databases
 Name |
Owner | Encoding | Collate | Ctype | Access privileges

-----------+----------+----------+-------------+-------------+-----------------------

postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | 
 template0 |
postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres +
 | | | | |
postgres=CTc/postgres
 template1 | postgres | UTF8 | en_US.UTF-8 |
en_US.UTF-8 | =c/postgres +
 | | | | | postgres=CTc/postgres
 whatnot |
postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |  

Unfortunately, when I try
to perform any DDL command on a server that sees "test2" database I receive
the following errors: 

postgres=# drop database test2;
ERROR: database
"test2" does not exist
postgres=# create database test2;
ERROR: database
"test2" already exists 

Also, when I try to remove another database called
"whatnot", drop operation never finishes. It looks like a transaction that
hangs some DDL operations: 

postgres=# select * from pgxc_prepared_xacts;

pgxc_prepared_xact 
--------------------
 T74589
(1 row)

postgres=# select
* from pg_prepared_xacts;
 transaction | gid | prepared | owner | database

-------------+--------+-------------------------------+----------+----------

73716 | T73716 | 2015-07-09 12:58:25.823385+02 | postgres | postgres
(1
row)

postgres=#  

When I try to rollback the transaction, Postgres says
that given GID does not exist. 

Is it a bug in Postgres XC? Is there a way
to synchronize the masters? (eg delete "test2" on one master and "whatnot"
on both of them). Please keep in mind that I created/dropped more databases
without any issues, so I'm unsure what went wrong in case of these two
specific databases. 

Cheers, 

Artur 

  

Because pgxc_ctl is highly recommended to configure PGXC cluster, I
have only old materials describing manual PGXC configuration.   This
material was used in PGXC session in Beijing, 2012.   Hope this helps.
  Please note that there are many pitfalls in manual configuration of
PGXC.

If you configure PGXC with pgxc_ctl, then I think you can learn much
more what you should be careful about.   You can find many hints of
PGXC configuration in pgxc_ctl source code.

Best;
---
Koichi Suzuki


2015-02-23 9:00 GMT+09:00 Erik Kooistra <emk...@gm...>:
> Hi,
>
> I have it configured manually. And i have set the node names as I want. Are there limitations to the node names. To they have to match the folder name ?
>
> Erik Kooistra
>
> On 20 feb. 2015, at 05:33, 鈴木 幸市 <ko...@in...> wrote:
>
>> Sorry for very late response.    How did you configure XC cluster?    If you did it manually, please examine your postgresql.conf file of the coordinator in question and see if coordinator’s node name are configured correctly.
>>
>> Regards;
>> ---
>> Koichi Suzuki
>> NTT DATA Intellilink Corp.
>> ko...@in...
>>
>>> 2015/02/06 22:42、Erik Kooistra <emk...@gm...> のメール：
>>>
>>> HI,
>>>
>>> I have setup 3 servers for postgres-xc following the guide on the wiki.
>>> The problem is that after everything is started and i try to connect to the postgres-xc instants as the postgrex-xc user
>>> I get the following error: "FATAL:  Coordinator cannot identify itself" I can't seem to find a different way to connect as
>>> superuser other then using the coordinator user.
>>>
>>> Erik Kooistra
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming. The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>>> look and join the conversation now. http://goparallel.sourceforge.net/_______________________________________________
>>> Postgres-xc-general mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Hi,

I have it configured manually. And i have set the node names as I want. Are there limitations to the node names. To they have to match the folder name ?

Erik Kooistra 
 
On 20 feb. 2015, at 05:33, 鈴木 幸市 <ko...@in...> wrote:

> Sorry for very late response.    How did you configure XC cluster?    If you did it manually, please examine your postgresql.conf file of the coordinator in question and see if coordinator’s node name are configured correctly.
> 
> Regards;
> ---
> Koichi Suzuki
> NTT DATA Intellilink Corp.
> ko...@in...
> 
>> 2015/02/06 22:42、Erik Kooistra <emk...@gm...> のメール：
>> 
>> HI,
>> 
>> I have setup 3 servers for postgres-xc following the guide on the wiki. 
>> The problem is that after everything is started and i try to connect to the postgres-xc instants as the postgrex-xc user
>> I get the following error: "FATAL:  Coordinator cannot identify itself" I can't seem to find a different way to connect as 
>> superuser other then using the coordinator user.
>> 
>> Erik Kooistra
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net/_______________________________________________
>> Postgres-xc-general mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> 

Sorry for very late response.    How did you configure XC cluster?    If you did it manually, please examine your postgresql.conf file of the coordinator in question and see if coordinator’s node name are configured correctly.

Regards;
---
Koichi Suzuki
NTT DATA Intellilink Corp.
ko...@in...

> 2015/02/06 22:42、Erik Kooistra <emk...@gm...> のメール：
> 
> HI,
> 
> I have setup 3 servers for postgres-xc following the guide on the wiki. 
> The problem is that after everything is started and i try to connect to the postgres-xc instants as the postgrex-xc user
> I get the following error: "FATAL:  Coordinator cannot identify itself" I can't seem to find a different way to connect as 
> superuser other then using the coordinator user.
> 
> Erik Kooistra
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/_______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

HI,

I have setup 3 servers for postgres-xc following the guide on the wiki. 
The problem is that after everything is started and i try to connect to the postgres-xc instants as the postgrex-xc user
I get the following error: "FATAL:  Coordinator cannot identify itself" I can't seem to find a different way to connect as 
superuser other then using the coordinator user.

Erik Kooistra

ah, thank you. that explains a lot. I am including the steps required to
ADD NODE and DELETE NODE from each table replica set as required.

so what happens if DISTRIBUTE BY REPLICATION is set for a table, and then
one of those datanodes loses connectivity? my initial testing indicates
that the rest of the cluster doesn't seem to notice a change, and data is
still accessible on a cluster-wide level (at which point it could be
possible to cleanly remove a malfunctioning node). is this not correct?

On Thu, Jan 8, 2015 at 5:01 PM, 鈴木 幸市 <ko...@in...> wrote:

>  Generally, XC itself does not provide a feature to deal with node
> failure.   You should configure slave of each node based upon log shipping.
>
>  Adding slaves can be done with “add node” command of pgxc_ctl.
>
>  Even with “distribute by replication”, XC requires all the replica are
> alive.
>  ---
> Koichi Suzuki
> NTT DATA Intellilink Corp.
> ko...@in...
>
>  2015/01/09 8:59、WilliamKray QFor <wil...@gm...> のメール：
>
>  Hello,
>
>  Apologies if these things have been discussed thousands of times before,
> but I'm feeling a bit frustrated.
>
>  Background:
> I'm running pgxc 1.2.1, and attempting to automate deploying a cluster in
> AWS. AWS, as we know, likes to drop servers without a lot of warning, and
> all kinds of bad things happen, so my main goal is having consistent data
> in the cluster in the event of a node failure, as well as easily adding a
> new node to replace the dropped one, or expand the cluster.
>
>  QUESTION 1:
> I'm under the impression that every table created in the database must be
> created with the DISTRIBUTE BY REPLICATION statement, if I want all data to
> be replicated, with no option to set that as the default method of
> distribution. Is this correct?
>
>
>  Please see the above comment.
>
>
>  QUESTION 2:
> I've also (in testing) created a database using some commands like the
> following:
> CREATE TABLE test (id int, data char(100));
> ALTER TABLE test DISTRIBUTE BY REPLICATION;
> misc. insert query here;
>
>  I then go to another node, and I can *access* all the data, but it is *not
> replicated to that node*. If I run:
> ALTER TABLE TO NODE (nodename);
>
>  it then appears to have data replicated to that node (as in, if I run EXECUTE
> DIRECT queries on that datanode, I can now see the content living on that
> node). BUT, when I remove any node from the cluster by running DROP NODE,
> suddenly none of the nodes have any data and the table is completely empty!
> HELP!
>
>
>  DROP NODE does not take care of the data.   It simply drops the node from
> pgxc_node system catalog.   If the dropped node is involved in any table,
> it will be suffered from catalog inconsistency, that is, pgxc_class
> contains dangling node information.   Before you issue DROP NODE, you
> should have issued ALTER TABLE DELETE NODE against each table dropping node
> is involved.
>
>   Are there more steps required to remove a node from a cluster? and if
> so, how do I configure my cluster to be resilient to node failure or
> unexpected server termination?
>
>  QUESTION 3:
> I've been looking into Postgres-XL, this appears to have a couple more
> features than PGXC, and more recent activity on their website, but also
> looks like it's the same codebase. Is XC still being maintained, or has
> development shifted to XL? Should I switch?
>
>
>  XL is, in fact, spin-off from XC.   Most of the code basis is the same.
> They’re still based upon PG 9.2 and does not have some new feature in 9.3.
> Anyway, they’re almost the same.
>
>
>  Thank you so much for your input. If this email is too long, please let
> me know and I'll break it up into more manageable chunks.
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now.
> http://goparallel.sourceforge.net_______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>
>

Generally, XC itself does not provide a feature to deal with node failure.   You should configure slave of each node based upon log shipping.

Adding slaves can be done with “add node” command of pgxc_ctl.

Even with “distribute by replication”, XC requires all the replica are alive.
---
Koichi Suzuki
NTT DATA Intellilink Corp.
ko...@in...<mailto:ko...@in...>.jp

2015/01/09 8:59、WilliamKray QFor <wil...@gm...<mailto:wil...@gm...>> のメール：

Hello,

Apologies if these things have been discussed thousands of times before, but I'm feeling a bit frustrated.

Background:
I'm running pgxc 1.2.1, and attempting to automate deploying a cluster in AWS. AWS, as we know, likes to drop servers without a lot of warning, and all kinds of bad things happen, so my main goal is having consistent data in the cluster in the event of a node failure, as well as easily adding a new node to replace the dropped one, or expand the cluster.

QUESTION 1:
I'm under the impression that every table created in the database must be created with the DISTRIBUTE BY REPLICATION statement, if I want all data to be replicated, with no option to set that as the default method of distribution. Is this correct?

Please see the above comment.


QUESTION 2:
I've also (in testing) created a database using some commands like the following:
CREATE TABLE test (id int, data char(100));
ALTER TABLE test DISTRIBUTE BY REPLICATION;
misc. insert query here;

I then go to another node, and I can access all the data, but it is not replicated to that node. If I run:
ALTER TABLE TO NODE (nodename);

it then appears to have data replicated to that node (as in, if I run EXECUTE DIRECT queries on that datanode, I can now see the content living on that node). BUT, when I remove any node from the cluster by running DROP NODE, suddenly none of the nodes have any data and the table is completely empty! HELP!

DROP NODE does not take care of the data.   It simply drops the node from pgxc_node system catalog.   If the dropped node is involved in any table, it will be suffered from catalog inconsistency, that is, pgxc_class contains dangling node information.   Before you issue DROP NODE, you should have issued ALTER TABLE DELETE NODE against each table dropping node is involved.

Are there more steps required to remove a node from a cluster? and if so, how do I configure my cluster to be resilient to node failure or unexpected server termination?

QUESTION 3:
I've been looking into Postgres-XL, this appears to have a couple more features than PGXC, and more recent activity on their website, but also looks like it's the same codebase. Is XC still being maintained, or has development shifted to XL? Should I switch?

XL is, in fact, spin-off from XC.   Most of the code basis is the same.   They’re still based upon PG 9.2 and does not have some new feature in 9.3.
Anyway, they’re almost the same.


Thank you so much for your input. If this email is too long, please let me know and I'll break it up into more manageable chunks.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net_______________________________________________
Postgres-xc-general mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

Hello,

Apologies if these things have been discussed thousands of times before,
but I'm feeling a bit frustrated.

Background:
I'm running pgxc 1.2.1, and attempting to automate deploying a cluster in
AWS. AWS, as we know, likes to drop servers without a lot of warning, and
all kinds of bad things happen, so my main goal is having consistent data
in the cluster in the event of a node failure, as well as easily adding a
new node to replace the dropped one, or expand the cluster.

QUESTION 1:
I'm under the impression that every table created in the database must be
created with the DISTRIBUTE BY REPLICATION statement, if I want all data to
be replicated, with no option to set that as the default method of
distribution. Is this correct?

QUESTION 2:
I've also (in testing) created a database using some commands like the
following:
CREATE TABLE test (id int, data char(100));
ALTER TABLE test DISTRIBUTE BY REPLICATION;
misc. insert query here;

I then go to another node, and I can *access* all the data, but it is *not
replicated to that node*. If I run:
ALTER TABLE TO NODE (nodename);

it then appears to have data replicated to that node (as in, if I run EXECUTE
DIRECT queries on that datanode, I can now see the content living on that
node). BUT, when I remove any node from the cluster by running DROP NODE,
suddenly none of the nodes have any data and the table is completely empty!
HELP!

Are there more steps required to remove a node from a cluster? and if so,
how do I configure my cluster to be resilient to node failure or unexpected
server termination?

QUESTION 3:
I've been looking into Postgres-XL, this appears to have a couple more
features than PGXC, and more recent activity on their website, but also
looks like it's the same codebase. Is XC still being maintained, or has
development shifted to XL? Should I switch?

Thank you so much for your input. If this email is too long, please let me
know and I'll break it up into more manageable chunks.

diff --git a/src/test/regress/expected/json_1.out b/src/test/regress/expected/json_1.out
index befe47d..04efaaa 100644
--- a/src/test/regress/expected/json_1.out
+++ b/src/test/regress/expected/json_1.out
@@ -386,7 +386,7 @@ CREATE TEMP TABLE rows AS
 SELECT x, 'txt' || x as y
 FROM generate_series(1,3) AS x;
 SELECT row_to_json(q,true)
-FROM rows q;
+FROM rows q order by x;
  row_to_json  
 --------------
  {"x":1,     +

Is there anyone review this patch?

Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

2014-12-25 10:57 GMT+08:00 Koichi Suzuki <koi...@gm...>:

> I appreciate for the patch.   Year, it's nice to keep both XL and XC
> synchronized.
>
> Best;
> ---
> Koichi Suzuki
>
>
> 2014-12-24 11:39 GMT+09:00 Jov <am...@am...>:
> > These changes already exist in PGXL,I port them to PGXC.
> >
> > the problem this patch solved(common in xl and xc):
> > 1.make pgxc_ctl explicit depend bash（report error if there is no bash
> > in PATH
> > ）
> > 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
> > 3.fix build error for missing .h for some type or maroc.
> > 4.fix pool send and recv fds which transfer corrupt fds
> >
> > There also some changes only for PGXC:
> > 1.build pgxc_ctl when cd contrib && make
> > 2.fix build error for postgresMain which declare as return void but
> return a
> > int.
> > 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
> > invalid in C99，which return int for a 64bit pointer，which cause runtime
> > error.
> >
> > ref:
> >
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
> >
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
> >
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
> >
> >
> > Jov
> > blog: http:amutu.com/blog
> >
> >
> >
> ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming! The Go Parallel Website,
> > sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> > hub for all things parallel software development, from weekly thought
> > leadership blogs to news, videos, case studies, tutorials and more. Take
> a
> > look and join the conversation now. http://goparallel.sourceforge.net
> > _______________________________________________
> > Postgres-xc-general mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >
>

I appreciate for the patch.   Year, it's nice to keep both XL and XC
synchronized.

Best;
---
Koichi Suzuki


2014-12-24 11:39 GMT+09:00 Jov <am...@am...>:
> These changes already exist in PGXL,I port them to PGXC.
>
> the problem this patch solved(common in xl and xc):
> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
> in PATH
> ）
> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
> 3.fix build error for missing .h for some type or maroc.
> 4.fix pool send and recv fds which transfer corrupt fds
>
> There also some changes only for PGXC:
> 1.build pgxc_ctl when cd contrib && make
> 2.fix build error for postgresMain which declare as return void but return a
> int.
> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
> invalid in C99，which return int for a 64bit pointer，which cause runtime
> error.
>
> ref:
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>
>
> Jov
> blog: http:amutu.com/blog
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

You are right,thanks!

patch updated.

Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

2014-12-24 13:55 GMT+08:00 Jaimin Pan <jai...@gm...>:

> Attachment for previous mail.
>
> 2014-12-24 13:54 GMT+08:00 Jaimin Pan <jai...@gm...>:
>
>> Hi Jov,
>>
>> I found the following change is also not in a proper way. Here is my
>> patch. Please tell me if I am wrong.
>>
>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>>
>> 2014-12-24 10:39 GMT+08:00 Jov <am...@am...>:
>>
>>> These changes already exist in PGXL,I port them to PGXC.
>>>
>>> the problem this patch solved(common in xl and xc):
>>> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
>>> in PATH
>>> ）
>>> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
>>> 3.fix build error for missing .h for some type or maroc.
>>> 4.fix pool send and recv fds which transfer corrupt fds
>>>
>>> There also some changes only for PGXC:
>>> 1.build pgxc_ctl when cd contrib && make
>>> 2.fix build error for postgresMain which declare as return void but
>>> return a int.
>>> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
>>> invalid in C99，which return int for a 64bit pointer，which cause runtime
>>> error.
>>>
>>> ref:
>>>
>>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
>>>
>>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>>>
>>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>>>
>>>
>>> Jov
>>> blog: http:amutu.com/blog <http://amutu.com/blog>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming! The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>> your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take
>>> a
>>> look and join the conversation now. http://goparallel.sourceforge.net
>>> _______________________________________________
>>> Postgres-xc-general mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>>
>>>
>>
>

Attachment for previous mail.

2014-12-24 13:54 GMT+08:00 Jaimin Pan <jai...@gm...>:

> Hi Jov,
>
> I found the following change is also not in a proper way. Here is my
> patch. Please tell me if I am wrong.
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>
> 2014-12-24 10:39 GMT+08:00 Jov <am...@am...>:
>
>> These changes already exist in PGXL,I port them to PGXC.
>>
>> the problem this patch solved(common in xl and xc):
>> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
>> in PATH
>> ）
>> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
>> 3.fix build error for missing .h for some type or maroc.
>> 4.fix pool send and recv fds which transfer corrupt fds
>>
>> There also some changes only for PGXC:
>> 1.build pgxc_ctl when cd contrib && make
>> 2.fix build error for postgresMain which declare as return void but
>> return a int.
>> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
>> invalid in C99，which return int for a 64bit pointer，which cause runtime
>> error.
>>
>> ref:
>>
>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
>>
>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>>
>> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>>
>>
>> Jov
>> blog: http:amutu.com/blog <http://amutu.com/blog>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming! The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is
>> your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net
>> _______________________________________________
>> Postgres-xc-general mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>>
>>
>

Hi Jov,

I found the following change is also not in a proper way. Here is my patch.
Please tell me if I am wrong.
http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/

2014-12-24 10:39 GMT+08:00 Jov <am...@am...>:

> These changes already exist in PGXL,I port them to PGXC.
>
> the problem this patch solved(common in xl and xc):
> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
> in PATH
> ）
> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
> 3.fix build error for missing .h for some type or maroc.
> 4.fix pool send and recv fds which transfer corrupt fds
>
> There also some changes only for PGXC:
> 1.build pgxc_ctl when cd contrib && make
> 2.fix build error for postgresMain which declare as return void but return
> a int.
> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
> invalid in C99，which return int for a 64bit pointer，which cause runtime
> error.
>
> ref:
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>
>
> Jov
> blog: http:amutu.com/blog <http://amutu.com/blog>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>

============== setting connection information         ==============
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
CREATE NODE
 pgxc_pool_reload
------------------
 t
(1 row)

 pgxc_pool_reload
------------------
 t
(1 row)

============== creating database "regression"         ==============
CREATE DATABASE
ALTER DATABASE
============== running regression test queries        ==============
test tablespace               ... ok
parallel group (18 tests):  oid name varchar uuid int2 float4 char boolean
txid int4 text money int8 float8 bit enum numeric rangetypes
     boolean                  ... ok
     char                     ... ok
     name                     ... ok
     varchar                  ... ok
     text                     ... ok
     int2                     ... ok
     int4                     ... ok
     int8                     ... ok
     oid                      ... ok
     float4                   ... ok
     float8                   ... ok
     bit                      ... ok
     numeric                  ... ok
     txid                     ... ok
     uuid                     ... ok
     enum                     ... ok
     money                    ... ok
     rangetypes               ... ok
test strings                  ... ok
test numerology               ... ok
parallel group (19 tests):  lseg comments box circle polygon path time
timetz abstime reltime interval tinterval inet point macaddr timestamp
tstypes timestamptz date
     point                    ... ok
     lseg                     ... ok
     box                      ... ok
     path                     ... ok
     polygon                  ... ok
     circle                   ... ok
     date                     ... ok
     time                     ... ok
     timetz                   ... ok
     timestamp                ... ok
     timestamptz              ... ok
     interval                 ... ok
     abstime                  ... ok
     reltime                  ... ok
     tinterval                ... ok
     inet                     ... ok
     macaddr                  ... ok
     tstypes                  ... ok
     comments                 ... ok
parallel group (6 tests):  regex geometry type_sanity horology oidjoins
opr_sanity
     geometry                 ... ok
     horology                 ... ok
     regex                    ... ok
     oidjoins                 ... ok
     type_sanity              ... ok
     opr_sanity               ... ok
test insert                   ... ok
test create_function_1        ... ok
test create_type              ... ok
test create_table             ... ok
test create_function_2        ... ok
parallel group (2 tests):  copyselect copy
     copy                     ... ok
     copyselect               ... ok
parallel group (2 tests):  create_operator create_misc
     create_misc              ... ok
     create_operator          ... ok
parallel group (2 tests):  create_view create_index
     create_index             ... ok
     create_view              ... ok
test inherit                  ... ok
parallel group (10 tests):  create_cast create_aggregate typed_table
create_function_3 drop_if_exists create_table_like constraints
updatable_views vacuum triggers
     create_aggregate         ... ok
     create_function_3        ... ok
     create_cast              ... ok
     constraints              ... ok
     triggers                 ... ok
     create_table_like        ... ok
     typed_table              ... ok
     vacuum                   ... ok
     drop_if_exists           ... ok
     updatable_views          ... ok
test sanity_check             ... ok
test errors                   ... ok
test select                   ... ok
parallel group (19 tests):  select_distinct_on btree_index select_having
hash_index select_distinct case update delete namespace select_implicit
random transactions select_into union arrays subselect portals join
aggregates
     select_into              ... ok
     select_distinct          ... ok
     select_distinct_on       ... ok
     select_implicit          ... ok
     select_having            ... ok
     subselect                ... ok
     union                    ... ok
     case                     ... ok
     join                     ... FAILED
     aggregates               ... ok
     transactions             ... ok
     random                   ... ok
     portals                  ... ok
     arrays                   ... ok
     btree_index              ... ok
     hash_index               ... ok
     update                   ... ok
     namespace                ... ok
     delete                   ... ok
test prepared_xacts           ... ok
parallel group (4 tests):  security_label collate privileges matview
     privileges               ... ok
     security_label           ... ok
     collate                  ... ok
     matview                  ... ok
parallel group (3 tests):  psql misc alter_generic
     alter_generic            ... ok
     misc                     ... ok
     psql                     ... ok
test rules                    ... ok
test event_trigger            ... ok
parallel group (15 tests):  combocid xmlmap tsdicts portals_p2 guc
dependency functional_deps cluster json tsearch foreign_data select_views
window foreign_key bitmapops
     select_views             ... ok
     portals_p2               ... ok
     foreign_key              ... ok
     cluster                  ... ok
     dependency               ... ok
     guc                      ... ok
     bitmapops                ... ok
     combocid                 ... ok
     tsearch                  ... ok
     tsdicts                  ... ok
     foreign_data             ... ok
     window                   ... ok
     xmlmap                   ... ok
     functional_deps          ... ok
     json                     ... FAILED
test advisory_lock            ... ok
parallel group (19 tests):  largeobject polymorphism prepare limit
returning rowtypes temp plancache conversion copy2 sequence xml truncate
with rangefuncs domain plpgsql alter_table without_oid
     plancache                ... ok
     limit                    ... ok
     plpgsql                  ... FAILED
     copy2                    ... ok
     temp                     ... ok
     domain                   ... ok
     rangefuncs               ... ok
     prepare                  ... ok
     without_oid              ... ok
     conversion               ... ok
     truncate                 ... ok
     alter_table              ... ok
     sequence                 ... ok
     polymorphism             ... FAILED (test process exited with exit
code 2)
     rowtypes                 ... ok
     returning                ... ok
     largeobject              ... FAILED (test process exited with exit
code 2)
     with                     ... ok
     xml                      ... ok
test stats                    ... ok
test xc_create_function       ... ok
test xc_misc                  ... ok
parallel group (17 tests):  xc_params xc_sequence xc_limit xc_constraints
xc_sort xc_having xc_temp xc_copy xc_distkey xc_FQS_join xc_remote xc_FQS
xc_trigship xc_triggers xc_groupby xc_alter_table xc_returning
     xc_groupby               ... ok
     xc_distkey               ... ok
     xc_having                ... ok
     xc_temp                  ... ok
     xc_remote                ... ok
     xc_FQS                   ... ok
     xc_FQS_join              ... ok
     xc_copy                  ... ok
     xc_alter_table           ... ok
     xc_sequence              ... ok
     xc_triggers              ... ok
     xc_trigship              ... ok
     xc_constraints           ... ok
     xc_limit                 ... ok
     xc_sort                  ... ok
     xc_returning             ... ok
     xc_params                ... ok
test xc_node                  ... ok
test xc_prepared_xacts        ... ok
test xc_notrans_block         ... ok
============== shutting down postmaster               ==============
waiting for server to shut down... done
server stopped

========================
 5 of 158 tests failed.
========================

This is regression result on FreeBSD after this patch.
I also run the regression on CentOS6 x86_64，which get 3 of 158 tests failed.
I will check the failed tests later.

Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

2014-12-24 10:39 GMT+08:00 Jov <am...@am...>:

> These changes already exist in PGXL,I port them to PGXC.
>
> the problem this patch solved(common in xl and xc):
> 1.make pgxc_ctl explicit depend bash（report error if there is no bash
> in PATH
> ）
> 2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
> 3.fix build error for missing .h for some type or maroc.
> 4.fix pool send and recv fds which transfer corrupt fds
>
> There also some changes only for PGXC:
> 1.build pgxc_ctl when cd contrib && make
> 2.fix build error for postgresMain which declare as return void but return
> a int.
> 3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
> invalid in C99，which return int for a 64bit pointer，which cause runtime
> error.
>
> ref:
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
>
> http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/
>
>
> Jov
> blog: http:amutu.com/blog <http://amutu.com/blog>
>
>

These changes already exist in PGXL,I port them to PGXC.

the problem this patch solved(common in xl and xc):
1.make pgxc_ctl explicit depend bash（report error if there is no bash
in PATH
）
2.change '#!/bin/bash' to '#/usr/bin/env bash' for all bash script
3.fix build error for missing .h for some type or maroc.
4.fix pool send and recv fds which transfer corrupt fds

There also some changes only for PGXC:
1.build pgxc_ctl when cd contrib && make
2.fix build error for postgresMain which declare as return void but return
a int.
3.fix warning : implicit declaration of function ‘heap_form_tuple’ is
invalid in C99，which return int for a 64bit pointer，which cause runtime
error.

ref:
http://sourceforge.net/p/postgres-xl/postgres-xl/ci/9f4da7c3527699ad66ed4af7088faa3ab8fad42c/
http://sourceforge.net/p/postgres-xl/postgres-xl/ci/ccaa2d54927b73ace8efc686ea715daa99a72a76/
http://sourceforge.net/p/postgres-xl/postgres-xl/ci/922f7aba30ee6a15a5cd4dabeeb254614d87d3b6/


Jov
blog: http:amutu.com/blog <http://amutu.com/blog>

Does anyone know of anyone using postgres-xc in a production environment?

Thanks!

Hello Afonso;

Thanks a lot for this presentation with your experience with XC.   I
visited the site and the proceedings looks only for the attendees.
Hope you can disclose your talk slide.

Regards;
---
Koichi Suzuki


2014-10-30 0:02 GMT+09:00 Afonso Bione <aag...@gm...>:
> Hello all,
> we are proud to announce our participation in E-Learn 2014
>
> http://www.editlib.org/search/?q=Afonso+Bione
>
>
> Enviado via iPad
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

Congratulations. Thanks for trying Postgres-XC and publishing a usecase.

On Fri, Oct 31, 2014 at 1:20 AM, Afonso Bione <aag...@gm...> wrote:

>
> Thanks for the comunity of postgres-xc.
>
> Integrating Moodle with a Postgres-XC cluster database providing high
> availability and high performance at a low cost
> <http://www.editlib.org/p/149006>Afonso Bione
> <http://www.editlib.org/index.cfm?author=Bione%2C%20Afonso>; Rodrigo de
> Souza <http://www.editlib.org/index.cfm?author=de%20Souza%2C%20Rodrigo>
>
> World Conference on E-Learning in Corporate, Government, Healthcare, and
> Higher Education Vol. 2014, No. 1 (Oct 27, 2014) pp. 1848–1853
>
> We study an integration of Moodle, a Virtual Learning Environment (VLE),
> with the distributed database system Postgres-XC, aiming at the
> construction of a pool of computers connected in parallel to ensure
> performance, as required by Moodle, at a low ...
>
> Topics: Implementation Examples & Issues,
> <http://www.editlib.org/search/?&topic=Implementation%20Examples%20%26%20Issues>Designing,
> Developing, and Assessing E-Learning
> <http://www.editlib.org/search/?&topic=Designing%2C%20Developing%2C%20and%20Assessing%20E%2DLearning>
>
>
> Enviado via iPad
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

Thanks for the comunity of postgres-xc.
 
Integrating Moodle with a Postgres-XC cluster database providing high availability and high performance at a low cost
Afonso Bione; Rodrigo de Souza
World Conference on E-Learning in Corporate, Government, Healthcare, and Higher Education Vol. 2014, No. 1 (Oct 27, 2014) pp. 1848–1853
We study an integration of Moodle, a Virtual Learning Environment (VLE), with the distributed database system Postgres-XC, aiming at the construction of a pool of computers connected in parallel to ensure performance, as required by Moodle, at a low ...
Topics: Implementation Examples & Issues, Designing, Developing, and Assessing E-Learning



Enviado via iPad

Hello all,
we are proud to announce our participation in E-Learn 2014

http://www.editlib.org/search/?q=Afonso+Bione


Enviado via iPad

I might have been wrong.   My colleague tried to do it with Heartbeat and couldn’t find how to do it.   Corosync may be better to handle it.

Thanks.
---
Koichi Suzuki

2014/10/20 19:58、Nikhil Sontakke <ni...@tr...<mailto:ni...@tr...>> のメール：

Hi Suzuki-san,

Yes, we have written custom resource Corosync/Pacemaker agents for failover of GTM to GTM-standby and also for failover of datanodes in Postgres-XL.

As Mason mentioned, the setup is a little complicated, but doable and yes we need to be a little careful about too eager failover.

Regards,
Nikhils

On Mon, Oct 20, 2014 at 3:27 PM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> wrote:
Does your configuration offer all the failover, including GTM,
datanode and coordinator?
---
Koichi Suzuki


2014-10-20 18:33 GMT+09:00 Mason Sharp <ms...@tr...<mailto:ms...@tr...>>:
>
>
> On Mon, Oct 20, 2014 at 11:19 AM, 鈴木 幸市 <ko...@in...<mailto:ko...@in...>> wrote:
>>
>> In HA, I don’t think Corosync/Pacemaker can deal with XC configuration,
>> where many components are interrelated and they are HA-aware.    At present,
>> Corosync/Pacemaker works well for HA-unaware components with master/slave
>> pair model.   XC configuration is more complicated than what they can deal
>> with.
>>
>
> We have configured with Corosync/Pacemaker. It is complex, however.
>
>
>
> --
> Mason Sharp
>
> TransLattice - http://www.translattice.com<http://www.translattice.com/>
> Clustered and Distributed Database Solutions
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...<mailto:Pos...@li...>
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Postgres-xc-general mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general



--
TransLattice - http://www.translattice.com<http://www.translattice.com/>
Distributed and Clustered Database Solutions
Postgres-XL Support

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho_______________________________________________
Postgres-xc-general mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

Hi Suzuki-san,

Yes, we have written custom resource Corosync/Pacemaker agents for failover
of GTM to GTM-standby and also for failover of datanodes in Postgres-XL.

As Mason mentioned, the setup is a little complicated, but doable and yes
we need to be a little careful about too eager failover.

Regards,
Nikhils

On Mon, Oct 20, 2014 at 3:27 PM, Koichi Suzuki <koi...@gm...>
wrote:

> Does your configuration offer all the failover, including GTM,
> datanode and coordinator?
> ---
> Koichi Suzuki
>
>
> 2014-10-20 18:33 GMT+09:00 Mason Sharp <ms...@tr...>:
> >
> >
> > On Mon, Oct 20, 2014 at 11:19 AM, 鈴木 幸市 <ko...@in...>
> wrote:
> >>
> >> In HA, I don’t think Corosync/Pacemaker can deal with XC configuration,
> >> where many components are interrelated and they are HA-aware.    At
> present,
> >> Corosync/Pacemaker works well for HA-unaware components with
> master/slave
> >> pair model.   XC configuration is more complicated than what they can
> deal
> >> with.
> >>
> >
> > We have configured with Corosync/Pacemaker. It is complex, however.
> >
> >
> >
> > --
> > Mason Sharp
> >
> > TransLattice - http://www.translattice.com
> > Clustered and Distributed Database Solutions
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Comprehensive Server Monitoring with Site24x7.
> > Monitor 10 servers for $9/Month.
> > Get alerted through email, SMS, voice calls or mobile push notifications.
> > Take corrective actions from your mobile device.
> > http://p.sf.net/sfu/Zoho
> > _______________________________________________
> > Postgres-xc-general mailing list
> > Pos...@li...
> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> >
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>



-- 
TransLattice - http://www.translattice.com
Distributed and Clustered Database Solutions
Postgres-XL Support

Does your configuration offer all the failover, including GTM,
datanode and coordinator?
---
Koichi Suzuki


2014-10-20 18:33 GMT+09:00 Mason Sharp <ms...@tr...>:
>
>
> On Mon, Oct 20, 2014 at 11:19 AM, 鈴木 幸市 <ko...@in...> wrote:
>>
>> In HA, I don’t think Corosync/Pacemaker can deal with XC configuration,
>> where many components are interrelated and they are HA-aware.    At present,
>> Corosync/Pacemaker works well for HA-unaware components with master/slave
>> pair model.   XC configuration is more complicated than what they can deal
>> with.
>>
>
> We have configured with Corosync/Pacemaker. It is complex, however.
>
>
>
> --
> Mason Sharp
>
> TransLattice - http://www.translattice.com
> Clustered and Distributed Database Solutions
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>