Menu
▾
▴
postgres-xc-general — General info and messages
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(19) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(12) |
Feb
(1) |
Mar
(4) |
Apr
(4) |
May
(32) |
Jun
(12) |
Jul
(11) |
Aug
(1) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(10) |
| 2012 |
Jan
(11) |
Feb
(1) |
Mar
(3) |
Apr
(25) |
May
(53) |
Jun
(38) |
Jul
(103) |
Aug
(54) |
Sep
(31) |
Oct
(66) |
Nov
(77) |
Dec
(20) |
| 2013 |
Jan
(91) |
Feb
(86) |
Mar
(103) |
Apr
(107) |
May
(25) |
Jun
(37) |
Jul
(17) |
Aug
(59) |
Sep
(38) |
Oct
(78) |
Nov
(29) |
Dec
(15) |
| 2014 |
Jan
(23) |
Feb
(82) |
Mar
(118) |
Apr
(101) |
May
(103) |
Jun
(45) |
Jul
(6) |
Aug
(10) |
Sep
|
Oct
(32) |
Nov
|
Dec
(9) |
| 2015 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael P. <mic...@gm...> - 2012-07-04 07:41:07
|
On Wed, Jul 4, 2012 at 2:31 PM, Joseph Glanville < jos...@or...> wrote: > Hey guys, > > This is more of a feature request/question regarding how HA could be > implemented with PostgreXC in the future. > > Could it be possible to have a composite table type which could > replicate to X nodes and distribute to Y nodes in such a way that > atleast X copies of every row is maintained but the table is shareded > across Y data nodes. > The answer is yes. It is possible. > > For example in a cluster of 6 nodes one would be able configure at > table with REPLICATION 2, DISTRIBUTE 3 BY HASH etc (I can't remember > what the table definitions look like) as such that the table would be > replicated to 2 sets of 3 nodes. > As you seem to be aware of, now XC only supports horizontal partitioning, meaning that tuples are present on each node in a complete form with all the column data. So let's call call your feature partial horizontal partitioning... Or something like this. > This is interesting becaues it can provide a flexible tradeoff between > full write scalability (current PostgresXC distribute) and full read > scalability (PostgresXC replicate or other slave solutions) > What is most useful about this setup is using PostgresXC this can be > maintained transparently without middleware and configured to be fully > sync multi-master etc. > Do you have some example of applications that may require that? > > Are there significant technical challenges to the above and is this > something the PostgresXC team would be interested in? > The code would need to be changed at many places and might require some effort especially for cursors and join determination at planner side. Another critical choice I see here is related to the preferential strategy for node choice. For example, in your case, the table is replicated on 3 nodes, and distributed on 3 nodes by hash. When a simple read query arrives at XC level, we need to make XC aware of which set of nodes to choose in priority. A simple session parameter which is table-based could manage that though, but is it user-friendly? A way to choose the set of nodes automatically would be to evaluate with a global system of statistics the load on each table of read/write operations for each set of nodes and choose the set of nodes the less loaded at the moment query is fired when planning it. This is largely more complicated however. -- Michael Paquier http://michael.otacoo.com |
|
From: Aris S. <ari...@gm...> - 2012-07-04 06:05:14
|
> XC planner is pretty smart, all the clauses are analyzed at the Coordinator level.
If I'm not mistaken, in WITH clause, after a first query run, many sub
of first query will be produced and these sub queries may produce
another queries too (or go to termination condition ). This is a run
time query.
Every sub query produced from another query will be send to
coordinator, to distributed to some of data nodes.
Consider this example from postgres documentation.
WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS (
SELECT g.id, g.link, g.data, 1,
ARRAY[ROW(g.f1, g.f2)],
false
FROM graph g
UNION ALL
SELECT g.id, g.link, g.data, sg.depth + 1,
path || ROW(g.f1, g.f2),
ROW(g.f1, g.f2) = ANY(path)
FROM graph g, search_graph sg
WHERE g.id = sg.link AND NOT cycle
)
SELECT * FROM search_graph;
I think many cross node join (intermediated with coordinator) will be happened.
And then WITH clause (in graph search case) will always longer
executed in a cluster than in a single node.
On 7/4/12, Michael Paquier <mic...@gm...> wrote:
> On Wed, Jul 4, 2012 at 2:38 PM, Aris Setyawan <ari...@gm...> wrote:
>
>> Hi All,
>>
>> > Hi Aris,
>> > We found that documents were not updated. WITH clause is supported in
>> XC. Please try
>> > to use it and let us know if it doesn't work for you. Thanks for
>> pointing it out.
>>
>> But how the coordinator will split the WITH clause (recursive) query?
>> If the query wrongly splitted, then many cross datanode join will
>> occurred.
>> This is a well known issue in a graph partitioned database.
>>
> XC planner is pretty smart, all the clauses are analyzed at the Coordinator
> level.
> Then only the necessary clauses and expressions are shipped to the
> necessary remote nodes depending on the table distribution.
> It may be possible that a lot of data is fetched back to Coordinator, but
> this depends on how you defined the table distribution strategy of your
> application.
> --
> Michael Paquier
> http://michael.otacoo.com
>
|
|
From: Joseph G. <jos...@or...> - 2012-07-04 05:57:03
|
Hey guys, This is more of a feature request/question regarding how HA could be implemented with PostgreXC in the future. Could it be possible to have a composite table type which could replicate to X nodes and distribute to Y nodes in such a way that atleast X copies of every row is maintained but the table is shareded across Y data nodes. For example in a cluster of 6 nodes one would be able configure at table with REPLICATION 2, DISTRIBUTE 3 BY HASH etc (I can't remember what the table definitions look like) as such that the table would be replicated to 2 sets of 3 nodes. This is interesting becaues it can provide a flexible tradeoff between full write scalability (current PostgresXC distribute) and full read scalability (PostgresXC replicate or other slave solutions) What is most useful about this setup is using PostgresXC this can be maintained transparently without middleware and configured to be fully sync multi-master etc. Are there significant technical challenges to the above and is this something the PostgresXC team would be interested in? Joseph. -- CTO | Orion Virtualisation Solutions | www.orionvm.com.au Phone: 1300 56 99 52 | Mobile: 0428 754 846 |
|
From: Michael P. <mic...@gm...> - 2012-07-04 05:42:04
|
On Wed, Jul 4, 2012 at 2:38 PM, Aris Setyawan <ari...@gm...> wrote: > Hi All, > > > Hi Aris, > > We found that documents were not updated. WITH clause is supported in > XC. Please try > > to use it and let us know if it doesn't work for you. Thanks for > pointing it out. > > But how the coordinator will split the WITH clause (recursive) query? > If the query wrongly splitted, then many cross datanode join will occurred. > This is a well known issue in a graph partitioned database. > XC planner is pretty smart, all the clauses are analyzed at the Coordinator level. Then only the necessary clauses and expressions are shipped to the necessary remote nodes depending on the table distribution. It may be possible that a lot of data is fetched back to Coordinator, but this depends on how you defined the table distribution strategy of your application. -- Michael Paquier http://michael.otacoo.com |
|
From: Aris S. <ari...@gm...> - 2012-07-04 05:38:14
|
Hi All, > Hi Aris, > We found that documents were not updated. WITH clause is supported in XC. Please try > to use it and let us know if it doesn't work for you. Thanks for pointing it out. But how the coordinator will split the WITH clause (recursive) query? If the query wrongly splitted, then many cross datanode join will occurred. This is a well known issue in a graph partitioned database. -thank's On 7/4/12, Michael Paquier <mic...@gm...> wrote: > On Wed, Jul 4, 2012 at 2:06 PM, Koichi Suzuki > <koi...@gm...>wrote: > >> Oh, could you provide an update to the document? >> > Done on GIT, you need to compile the docs. > The documentation updated will be released on postgres-XC website at the > same time as 1.0.1. > > Thanks. > > >> ---------- >> Koichi Suzuki >> >> >> 2012/7/4 Ashutosh Bapat <ash...@en...>: >> > Hi Aris, >> > We found that documents were not updated. WITH clause is supported in >> > XC. >> > Please try to use it and let us know if it doesn't work for you. Thanks >> for >> > pointing it out. >> > >> > >> > On Sat, Jun 30, 2012 at 11:47 AM, Aris Setyawan <ari...@gm...> >> wrote: >> >> >> >> Hi, >> >> >> >> I have use a case that need to (manually using gearman) split a >> >> postgre recursive query to a numbers of replication node, to execute >> >> it faster. >> >> >> >> Since I will use postgre-xc cluster, is it possible to connect a >> >> (postgresql) data node server (a relpica in my case above) directly >> >> (not using coordiantor)? >> >> >> >> thank's. >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Live Security Virtual Conference >> >> Exclusive live event will cover all the ways today's security and >> >> threat landscape has changed and how IT managers can respond. >> Discussions >> >> will include endpoint security, mobile security and the latest in >> malware >> >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> >> _______________________________________________ >> >> Postgres-xc-general mailing list >> >> Pos...@li... >> >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > >> > >> > >> > >> > -- >> > Best Wishes, >> > Ashutosh Bapat >> > EntepriseDB Corporation >> > The Enterprise Postgres Company >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference >> > Exclusive live event will cover all the ways today's security and >> > threat landscape has changed and how IT managers can respond. >> > Discussions >> > will include endpoint security, mobile security and the latest in >> > malware >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> > _______________________________________________ >> > Postgres-xc-general mailing list >> > Pos...@li... >> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> > > > > -- > Michael Paquier > http://michael.otacoo.com > |
|
From: Michael P. <mic...@gm...> - 2012-07-04 05:08:25
|
On Wed, Jul 4, 2012 at 2:06 PM, Koichi Suzuki <koi...@gm...>wrote: > Oh, could you provide an update to the document? > Done on GIT, you need to compile the docs. The documentation updated will be released on postgres-XC website at the same time as 1.0.1. Thanks. > ---------- > Koichi Suzuki > > > 2012/7/4 Ashutosh Bapat <ash...@en...>: > > Hi Aris, > > We found that documents were not updated. WITH clause is supported in XC. > > Please try to use it and let us know if it doesn't work for you. Thanks > for > > pointing it out. > > > > > > On Sat, Jun 30, 2012 at 11:47 AM, Aris Setyawan <ari...@gm...> > wrote: > >> > >> Hi, > >> > >> I have use a case that need to (manually using gearman) split a > >> postgre recursive query to a numbers of replication node, to execute > >> it faster. > >> > >> Since I will use postgre-xc cluster, is it possible to connect a > >> (postgresql) data node server (a relpica in my case above) directly > >> (not using coordiantor)? > >> > >> thank's. > >> > >> > >> > ------------------------------------------------------------------------------ > >> Live Security Virtual Conference > >> Exclusive live event will cover all the ways today's security and > >> threat landscape has changed and how IT managers can respond. > Discussions > >> will include endpoint security, mobile security and the latest in > malware > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >> _______________________________________________ > >> Postgres-xc-general mailing list > >> Pos...@li... > >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > > > > > > > -- > > Best Wishes, > > Ashutosh Bapat > > EntepriseDB Corporation > > The Enterprise Postgres Company > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- Michael Paquier http://michael.otacoo.com |
|
From: Koichi S. <koi...@gm...> - 2012-07-04 05:07:01
|
Oh, could you provide an update to the document? ---------- Koichi Suzuki 2012/7/4 Ashutosh Bapat <ash...@en...>: > Hi Aris, > We found that documents were not updated. WITH clause is supported in XC. > Please try to use it and let us know if it doesn't work for you. Thanks for > pointing it out. > > > On Sat, Jun 30, 2012 at 11:47 AM, Aris Setyawan <ari...@gm...> wrote: >> >> Hi, >> >> I have use a case that need to (manually using gearman) split a >> postgre recursive query to a numbers of replication node, to execute >> it faster. >> >> Since I will use postgre-xc cluster, is it possible to connect a >> (postgresql) data node server (a relpica in my case above) directly >> (not using coordiantor)? >> >> thank's. >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: Ashutosh B. <ash...@en...> - 2012-07-04 04:23:35
|
Hi Aris, We found that documents were not updated. WITH clause is supported in XC. Please try to use it and let us know if it doesn't work for you. Thanks for pointing it out. On Sat, Jun 30, 2012 at 11:47 AM, Aris Setyawan <ari...@gm...> wrote: > Hi, > > I have use a case that need to (manually using gearman) split a > postgre recursive query to a numbers of replication node, to execute > it faster. > > Since I will use postgre-xc cluster, is it possible to connect a > (postgresql) data node server (a relpica in my case above) directly > (not using coordiantor)? > > thank's. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Ashutosh B. <ash...@en...> - 2012-07-02 04:15:08
|
Aris, Ideally you shouldn't need to execute queries against datanode (except for say debugging purpose). The distribute execution of the query is responsibility of the coordinator. The application need not think about it. Can you please provide an example of the query and why do you need to connect to the datanode? On Sat, Jun 30, 2012 at 1:27 PM, Koichi Suzuki <koi...@gm...>wrote: > Safer way is to use EXECUTE DIRECT. It is physically possible to > connect psql to datanode directly but because transactions are not > controlled by GTM in this case, you cannot guarantee the visibility > and the data integrity. > > Regards; > ---------- > Koichi Suzuki > > > 2012/6/30 Aris Setyawan <ari...@gm...>: > > Hi, > > > > I have use a case that need to (manually using gearman) split a > > postgre recursive query to a numbers of replication node, to execute > > it faster. > > > > Since I will use postgre-xc cluster, is it possible to connect a > > (postgresql) data node server (a relpica in my case above) directly > > (not using coordiantor)? > > > > thank's. > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Koichi S. <koi...@gm...> - 2012-06-30 07:57:10
|
Safer way is to use EXECUTE DIRECT. It is physically possible to connect psql to datanode directly but because transactions are not controlled by GTM in this case, you cannot guarantee the visibility and the data integrity. Regards; ---------- Koichi Suzuki 2012/6/30 Aris Setyawan <ari...@gm...>: > Hi, > > I have use a case that need to (manually using gearman) split a > postgre recursive query to a numbers of replication node, to execute > it faster. > > Since I will use postgre-xc cluster, is it possible to connect a > (postgresql) data node server (a relpica in my case above) directly > (not using coordiantor)? > > thank's. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |
|
From: Aris S. <ari...@gm...> - 2012-06-30 06:18:01
|
Hi, I have use a case that need to (manually using gearman) split a postgre recursive query to a numbers of replication node, to execute it faster. Since I will use postgre-xc cluster, is it possible to connect a (postgresql) data node server (a relpica in my case above) directly (not using coordiantor)? thank's. |
|
From: Neil M. <nm...@xu...> - 2012-06-25 13:08:50
|
Thanks to all for the tips, all up and running now ! PS , on the short version of documentation, it does not mentioned the HOST parameter: http://postgres-xc.sourceforge.net/docs/1_0/install-short.html Though I am guessing it all works fine when installed on the same machine Thanks again Neil ________________________________________ From: Michael Paquier [mic...@gm...] Sent: Monday, June 25, 2012 2:09 AM To: Neil Mooney Cc: pos...@li... Subject: Re: [Postgres-xc-general] createdb: database creation failed: ERROR: Failed to get pooled connections On Mon, Jun 25, 2012 at 10:07 AM, Michael Paquier <mic...@gm...<mailto:mic...@gm...>> wrote: I may be stepping someone's else answer... But here is some input. On Fri, Jun 22, 2012 at 9:30 PM, Neil Mooney <nm...@xu...<mailto:nm...@xu...>> wrote: Can anyone point out where I am going wrong here ? Here is a complete log of what i've done to setup , error at the end: Data/Coordinator machines: ========================== node1: ====== rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_coordinator1 mkdir -p /opt/postgres/data_datanode1 chown postgres: /opt/postgres/data_* su - postgres initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 initdb -D /opt/postgres/data_datanode1 --nodename datanode1 #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server #configure /opt/postgres/data_datanode1/postgres.conf with GTM server postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & node2: ====== rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_coordinator2 mkdir -p /opt/postgres/data_datanode2 chown postgres: /opt/postgres/data_* su - postgres initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 initdb -D /opt/postgres/data_datanode2 --nodename datanode2 #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server #configure /opt/postgres/data_datanode2/postgres.conf with GTM server postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & each coordinator node: ====================== postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & You already started your nodes at an earlier step, so this is not necessary. An error would be returned telling that node is already started like postgres. GTM machine: ============= rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_gtm chown postgres: /opt/postgres/data* su - postgres initgtm -D /opt/postgres/data_gtm -Z gtm gtm -D /opt/postgres/data_gtm >logfile 2>&1 & You should start GTM before starting your 2 Coordinators and your 2 Datanodes. Postgres-XC nodes need to register on GTM at start-up or they cannot start. Registering Nodes: (all datanodes ??? has been done on both, output below) ================== psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" postgres psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" postgres psql -c "SELECT pgxc_pool_reload()" postgres select oid,node_name from pgxc_node; Here you have to launch CREATE NODE and pgxc_pool_reload on each Coordinator. When you start up a node this node knows only about itself, so you need to register all the other Coordinators and Datanodes. Registering other Coordinators on a Coordinator is mandatory or you won't be able to synchronize DDL among Coordinators, this could result in a table being created on a Coordinator and not another. So, in your case, launch the following queries: - On Coordinator 1: CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = '$node1_ip'); CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = '$node2_ip'); CREATE NODE coordinator2 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node2_ip'); - On Coordinator 2: CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = '$node1_ip'); CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = '$node2_ip'); CREATE NODE coordinator1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node2_ip'); There is a mistake here. On Coordinator 2, coordinator1 should be registered with a host set to $node1_ip, resulting in: CREATE NODE coordinator1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node1_ip'); -- Michael Paquier http://michael.otacoo.com |
|
From: Michael P. <mic...@gm...> - 2012-06-25 01:10:08
|
On Mon, Jun 25, 2012 at 10:07 AM, Michael Paquier <mic...@gm... > wrote: > I may be stepping someone's else answer... But here is some input. > > On Fri, Jun 22, 2012 at 9:30 PM, Neil Mooney <nm...@xu...> wrote: > >> Can anyone point out where I am going wrong here ? >> >> Here is a complete log of what i've done to setup , error at the end: >> >> Data/Coordinator machines: >> ========================== >> >> node1: >> ====== >> >> rm -fr /opt/postgres/data* >> >> mkdir -p /opt/postgres/data_coordinator1 >> mkdir -p /opt/postgres/data_datanode1 >> >> chown postgres: /opt/postgres/data_* >> >> su - postgres >> >> initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 >> initdb -D /opt/postgres/data_datanode1 --nodename datanode1 >> >> #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server >> #configure /opt/postgres/data_datanode1/postgres.conf with GTM server >> >> >> postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & >> postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & >> >> node2: >> ====== >> >> rm -fr /opt/postgres/data* >> >> mkdir -p /opt/postgres/data_coordinator2 >> mkdir -p /opt/postgres/data_datanode2 >> >> chown postgres: /opt/postgres/data_* >> >> su - postgres >> >> initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 >> initdb -D /opt/postgres/data_datanode2 --nodename datanode2 >> >> #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server >> #configure /opt/postgres/data_datanode2/postgres.conf with GTM server >> >> postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & >> postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & >> >> each coordinator node: >> ====================== >> >> postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & >> > You already started your nodes at an earlier step, so this is not > necessary. > An error would be returned telling that node is already started like > postgres. > >> GTM machine: >> ============= >> >> rm -fr /opt/postgres/data* >> >> mkdir -p /opt/postgres/data_gtm >> >> chown postgres: /opt/postgres/data* >> >> su - postgres >> >> initgtm -D /opt/postgres/data_gtm -Z gtm >> gtm -D /opt/postgres/data_gtm >logfile 2>&1 & >> > You should start GTM *before* starting your 2 Coordinators and your 2 > Datanodes. > Postgres-XC nodes need to register on GTM at start-up or they cannot start. > > >> >> Registering Nodes: (all datanodes ??? has been done on both, output below) >> ================== >> >> psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" >> postgres >> psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" >> postgres >> psql -c "SELECT pgxc_pool_reload()" postgres >> select oid,node_name from pgxc_node; >> > > Here you have to launch CREATE NODE and pgxc_pool_reload on *each > Coordinator*. When you start up a node this node knows only about itself, > so you need to register all the other Coordinators and Datanodes. > Registering other Coordinators on a Coordinator is mandatory or you won't > be able to synchronize DDL among Coordinators, this could result in a table > being created on a Coordinator and not another. > > So, in your case, launch the following queries: > - On Coordinator 1: > CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = > '$node1_ip'); > CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = > '$node2_ip'); > CREATE NODE coordinator2 WITH (TYPE = 'coordinator', PORT = 5432, HOST = > '$node2_ip'); > - On Coordinator 2: > CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = > '$node1_ip'); > CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = > '$node2_ip'); > CREATE NODE coordinator1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = > '$node2_ip'); > There is a mistake here. On Coordinator 2, coordinator1 should be registered with a host set to $node1_ip, resulting in: CREATE NODE coordinator1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node1_ip'); -- Michael Paquier http://michael.otacoo.com |
|
From: Michael P. <mic...@gm...> - 2012-06-25 01:07:27
|
I may be stepping someone's else answer... But here is some input. On Fri, Jun 22, 2012 at 9:30 PM, Neil Mooney <nm...@xu...> wrote: > Can anyone point out where I am going wrong here ? > > Here is a complete log of what i've done to setup , error at the end: > > Data/Coordinator machines: > ========================== > > node1: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator1 > mkdir -p /opt/postgres/data_datanode1 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 > initdb -D /opt/postgres/data_datanode1 --nodename datanode1 > > #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server > #configure /opt/postgres/data_datanode1/postgres.conf with GTM server > > > postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > > node2: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator2 > mkdir -p /opt/postgres/data_datanode2 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 > initdb -D /opt/postgres/data_datanode2 --nodename datanode2 > > #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server > #configure /opt/postgres/data_datanode2/postgres.conf with GTM server > > postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & > > each coordinator node: > ====================== > > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > You already started your nodes at an earlier step, so this is not necessary. An error would be returned telling that node is already started like postgres. > GTM machine: > ============= > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_gtm > > chown postgres: /opt/postgres/data* > > su - postgres > > initgtm -D /opt/postgres/data_gtm -Z gtm > gtm -D /opt/postgres/data_gtm >logfile 2>&1 & > You should start GTM *before* starting your 2 Coordinators and your 2 Datanodes. Postgres-XC nodes need to register on GTM at start-up or they cannot start. > > Registering Nodes: (all datanodes ??? has been done on both, output below) > ================== > > psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" > postgres > psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" > postgres > psql -c "SELECT pgxc_pool_reload()" postgres > select oid,node_name from pgxc_node; > Here you have to launch CREATE NODE and pgxc_pool_reload on *each Coordinator*. When you start up a node this node knows only about itself, so you need to register all the other Coordinators and Datanodes. Registering other Coordinators on a Coordinator is mandatory or you won't be able to synchronize DDL among Coordinators, this could result in a table being created on a Coordinator and not another. So, in your case, launch the following queries: - On Coordinator 1: CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = '$node1_ip'); CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = '$node2_ip'); CREATE NODE coordinator2 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node2_ip'); - On Coordinator 2: CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432, HOST = '$node1_ip'); CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433, HOST = '$node2_ip'); CREATE NODE coordinator1 WITH (TYPE = 'coordinator', PORT = 5432, HOST = '$node2_ip'); In the case of node1, datanode1 and coordinator1 are on the same node. So you can replace $node1_ip with localhost or 127.0.0.1 when defining datanode1 for coordinator1. Same for node node2, datanode2 and coordinator2 are on the same node. So you can replace $node2_ip with localhost or 127.0.0.1 when defining datanode2 for coordinator2. > #output > > node1: > postgres=# select oid,node_name from pgxc_node; > oid | node_name > -------+-------------- > 11129 | coordinator1 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > This output is incorrect. Coordinator 1 is not aware of Coordinator 2. Coordinator 1 also thinks that datanode2 is on node1 as you did not define an IP to redirect correctly. > > > node2: > [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" > postgres > oid | node_name > -------+-------------- > 11129 | coordinator2 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > Same here, Coordinator 1 is not aware of Coordinator2. Coordinator2 thinks that datanode1 is on the same server, which is not the case as it looks that coordinator2/datanode2 and coordinator1/datanode1 are grouped on 2 different nodes. > > Creating DB's : > =============== > > [postgres@las1-app014 ~]$ createdb test > createdb: database creation failed: ERROR: Failed to get pooled > connections > Here I guess you are connecting to coordinator1. This error happens because coordinator1 cannot connect to datanode2, as it is not located on local server but on server node2. Regards, -- Michael Paquier http://michael.otacoo.com |
|
From: Abbas B. <abb...@en...> - 2012-06-22 16:38:47
|
I just spotted another mistake in data node creation. You are creating both the data nodes on both the coordinators with the default IP i.e. 127.0.0.1 which is not true for datanode1 when created on coordinator2. Similarly it is not true for datanode2 on coordinator1. It would be good idea to create both data nodes by explicitly specifying the IP addresses. So the queries should look something like this. psql -c "CREATE NODE datanode1 WITH (HOST = 'IP_OF_datanode1', TYPE = 'datanode', PORT = 15432)" postgres psql -c "CREATE NODE datanode2 WITH (HOST = 'IP_OF_datanode2', TYPE = 'datanode', PORT = 15433)" postgres psql -c "CREATE NODE coordinator1 WITH (HOST = '10.152.14.24', type = 'coordinator', PORT = 5432);" postgres psql -c "CREATE NODE coordinator2 WITH (HOST = '10.152.14.25', type = 'coordinator', PORT = 5432);" postgres If this does not work and gives the same error please provide the output of psql -c "select oid,* from pgxc_node;" postgres by running on the coordinator2. On Fri, Jun 22, 2012 at 7:06 PM, Neil Mooney <nm...@xu...> wrote: > Thanks to Magorn and Abbass for their input. > > I followed your advice RE: creating new coordinator nodes in the db with > the following query on both nodes: > > psql -c "DROP NODE coordinator1" postgres > psql -c "DROP NODE coordinator2" postgres > psql -c "CREATE NODE coordinator1 WITH (HOST = '10.152.14.24', type = > 'coordinator', PORT = 5432);" postgres > psql -c "CREATE NODE coordinator2 WITH (HOST = '10.152.14.25', type = > 'coordinator', PORT = 5432);" postgres > psql -c "SELECT pgxc_pool_reload()" postgres > > I am still seeing a problem, logfile indicates connectivity between the > two data nodes, telnet-ing the port seems to work ok. > > [postgres@las1-app015 ~]$ cat logfile > > LOG: database system was interrupted; last known up at 2012-06-22 > 13:31:58 UTC > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: record with zero length at 0/1776A90 > LOG: redo is not required > LOG: autovacuum launcher started > LOG: database system is ready to accept connections > LOG: database system was interrupted; last known up at 2012-06-22 > 13:32:20 UTC > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: redo starts at 0/177F970 > LOG: record with zero length at 0/177FB60 > LOG: redo done at 0/177FB20 > LOG: last completed transaction was at log time 2012-06-22 > 13:34:59.977913+00 > LOG: autovacuum launcher started > LOG: database system is ready to accept connections > LOG: incomplete startup packet > LOG: incomplete startup packet > LOG: failed to connect to Datanode > WARNING: can not connect to node 16384 > LOG: failed to acquire connections > STATEMENT: CREATE DATABASE test; > > ERROR: Failed to get pooled connections > STATEMENT: CREATE DATABASE test; > > [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" > postgres > oid | node_name > -------+-------------- > 11129 | coordinator2 > 16384 | datanode1 > 16385 | datanode2 > 24583 | coordinator1 > (4 rows) > > [postgres@las1-app015 ~]$ telnet las1-app014 15432 > Trying 10.152.14.24... > Connected to las1-app014. > Escape character is '^]'. > ^] > > telnet> quit > Connection closed. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- -- Abbas Architect EnterpriseDB Corporation The Enterprise PostgreSQL Company Phone: 92-334-5100153 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. |
|
From: Neil M. <nm...@xu...> - 2012-06-22 14:06:52
|
Thanks to Magorn and Abbass for their input. I followed your advice RE: creating new coordinator nodes in the db with the following query on both nodes: psql -c "DROP NODE coordinator1" postgres psql -c "DROP NODE coordinator2" postgres psql -c "CREATE NODE coordinator1 WITH (HOST = '10.152.14.24', type = 'coordinator', PORT = 5432);" postgres psql -c "CREATE NODE coordinator2 WITH (HOST = '10.152.14.25', type = 'coordinator', PORT = 5432);" postgres psql -c "SELECT pgxc_pool_reload()" postgres I am still seeing a problem, logfile indicates connectivity between the two data nodes, telnet-ing the port seems to work ok. [postgres@las1-app015 ~]$ cat logfile LOG: database system was interrupted; last known up at 2012-06-22 13:31:58 UTC LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/1776A90 LOG: redo is not required LOG: autovacuum launcher started LOG: database system is ready to accept connections LOG: database system was interrupted; last known up at 2012-06-22 13:32:20 UTC LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 0/177F970 LOG: record with zero length at 0/177FB60 LOG: redo done at 0/177FB20 LOG: last completed transaction was at log time 2012-06-22 13:34:59.977913+00 LOG: autovacuum launcher started LOG: database system is ready to accept connections LOG: incomplete startup packet LOG: incomplete startup packet LOG: failed to connect to Datanode WARNING: can not connect to node 16384 LOG: failed to acquire connections STATEMENT: CREATE DATABASE test; ERROR: Failed to get pooled connections STATEMENT: CREATE DATABASE test; [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" postgres oid | node_name -------+-------------- 11129 | coordinator2 16384 | datanode1 16385 | datanode2 24583 | coordinator1 (4 rows) [postgres@las1-app015 ~]$ telnet las1-app014 15432 Trying 10.152.14.24... Connected to las1-app014. Escape character is '^]'. ^] telnet> quit Connection closed. |
|
From: Abbas B. <abb...@en...> - 2012-06-22 13:06:59
|
You have 2 data nodes and 2 coordinators in the cluster. In this case you need to create coordinator1 on coordinator2 and coordinator2 on coordinator1. You need to add some thing similar to these queries when creating nodes on each of the coordinators. On coordinator1 CREATE NODE coordinator2 WITH (HOST = 'IP_OF_coordinator2_HERE', type = 'coordinator', PORT = 5432); and On coordinator2 CREATE NODE coordinator1 WITH (HOST = 'IP_OF_coordinator1_HERE', type = 'coordinator', PORT = 5432); Thanks. On Fri, Jun 22, 2012 at 5:30 PM, Neil Mooney <nm...@xu...> wrote: > Can anyone point out where I am going wrong here ? > > Here is a complete log of what i've done to setup , error at the end: > > Data/Coordinator machines: > ========================== > > node1: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator1 > mkdir -p /opt/postgres/data_datanode1 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 > initdb -D /opt/postgres/data_datanode1 --nodename datanode1 > > #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server > #configure /opt/postgres/data_datanode1/postgres.conf with GTM server > > > postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > > node2: > ====== > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_coordinator2 > mkdir -p /opt/postgres/data_datanode2 > > chown postgres: /opt/postgres/data_* > > su - postgres > > initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 > initdb -D /opt/postgres/data_datanode2 --nodename datanode2 > > #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server > #configure /opt/postgres/data_datanode2/postgres.conf with GTM server > > postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & > postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & > > each coordinator node: > ====================== > > postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & > > > tail -f log > > GTM machine: > ============= > > rm -fr /opt/postgres/data* > > mkdir -p /opt/postgres/data_gtm > > chown postgres: /opt/postgres/data* > > su - postgres > > initgtm -D /opt/postgres/data_gtm -Z gtm > gtm -D /opt/postgres/data_gtm >logfile 2>&1 & > > Registering Nodes: (all datanodes ??? has been done on both, output below) > ================== > > psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" > postgres > psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" > postgres > psql -c "SELECT pgxc_pool_reload()" postgres > select oid,node_name from pgxc_node; > > #output > > node1: > postgres=# select oid,node_name from pgxc_node; > oid | node_name > -------+-------------- > 11129 | coordinator1 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > > > node2: > [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" > postgres > oid | node_name > -------+-------------- > 11129 | coordinator2 > 16384 | datanode1 > 16385 | datanode2 > (3 rows) > > > > > Creating DB's : > =============== > > [postgres@las1-app014 ~]$ createdb test > createdb: database creation failed: ERROR: Failed to get pooled > connections > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- -- Abbas Architect EnterpriseDB Corporation The Enterprise PostgreSQL Company Phone: 92-334-5100153 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. |
|
From: Neil M. <nm...@xu...> - 2012-06-22 12:47:00
|
Can anyone point out where I am going wrong here ? Here is a complete log of what i've done to setup , error at the end: Data/Coordinator machines: ========================== node1: ====== rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_coordinator1 mkdir -p /opt/postgres/data_datanode1 chown postgres: /opt/postgres/data_* su - postgres initdb -D /opt/postgres/data_coordinator1 --nodename coordinator1 initdb -D /opt/postgres/data_datanode1 --nodename datanode1 #configure /opt/postgres/data_coordinator1/postgres.conf with GTM server #configure /opt/postgres/data_datanode1/postgres.conf with GTM server postgres -X -p 15432 -D /opt/postgres/data_datanode1 >>logfile 2>&1 & postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & node2: ====== rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_coordinator2 mkdir -p /opt/postgres/data_datanode2 chown postgres: /opt/postgres/data_* su - postgres initdb -D /opt/postgres/data_coordinator2 --nodename coordinator2 initdb -D /opt/postgres/data_datanode2 --nodename datanode2 #configure /opt/postgres/data_coordinator2/postgres.conf with GTM server #configure /opt/postgres/data_datanode2/postgres.conf with GTM server postgres -X -p 15433 -D /opt/postgres/data_datanode2 >>logfile 2>&1 & postgres -C -D /opt/postgres/data_coordinator2 >>logfile 2>&1 & each coordinator node: ====================== postgres -C -D /opt/postgres/data_coordinator1 >>logfile 2>&1 & tail -f log GTM machine: ============= rm -fr /opt/postgres/data* mkdir -p /opt/postgres/data_gtm chown postgres: /opt/postgres/data* su - postgres initgtm -D /opt/postgres/data_gtm -Z gtm gtm -D /opt/postgres/data_gtm >logfile 2>&1 & Registering Nodes: (all datanodes ??? has been done on both, output below) ================== psql -c "CREATE NODE datanode1 WITH (TYPE = 'datanode', PORT = 15432)" postgres psql -c "CREATE NODE datanode2 WITH (TYPE = 'datanode', PORT = 15433)" postgres psql -c "SELECT pgxc_pool_reload()" postgres select oid,node_name from pgxc_node; #output node1: postgres=# select oid,node_name from pgxc_node; oid | node_name -------+-------------- 11129 | coordinator1 16384 | datanode1 16385 | datanode2 (3 rows) node2: [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;" postgres oid | node_name -------+-------------- 11129 | coordinator2 16384 | datanode1 16385 | datanode2 (3 rows) Creating DB's : =============== [postgres@las1-app014 ~]$ createdb test createdb: database creation failed: ERROR: Failed to get pooled connections |
|
From: Mason S. <ma...@st...> - 2012-06-12 03:44:18
|
XC speaks the same wire level protocol as PostgreSQL, so all drivers and connectors should in theory work. Sent from my IPhone On Jun 11, 2012, at 8:13 AM, Fernando Lozano <fer...@lo...> wrote: > Hi Michael, > > Found the offending text. It's in the README from many releases, including 1.0.0: > > Postgres-XC is aiming to provide transparent access to the database, which means one can use existing PostgreSQL application as is. For implementation reason, > ***transparency level is limited to access via libpq libraries*** > and simple statements as found in the Architecture Document in the release material. > > PHP, Perl and most users won't be bothered because those language drivers use libpq, but Java developers use a pure-java JDBC driver which does not uses libpq at all. > > This statement on the README may be understood as "there are changes to libpq in postgresql-xc so you have to use our libpq. Other clients won't work". > > But as I understand you reply, I can use any libpq to access postgresql-xc without problem. For example, a pgAdminIII binary for windows that I already use for a plain PostgreSQL server should work out-of-the-box with PostgreSQL-XC, or the rpm files from Debian Linux for a PHP app. And I could also use other clients, not based on libpq, such as a JDBC driver anda a .Net provider, right? > > > []s, Fernando Lozano > >> Hi, >> >> I spent half an hour browsing the website, wiki and docs and could not find where I read that postgresql-xc should be transparent to libpq clients. Will keep looking later. >> >> >> []s, Fernando Lozano >> >> >>> Hi, >>> >>> You should avoid sending responses to Postgres announce mailing lists people are going to complain. Better to use the MLs dedicated to xc. >>> Please find my answers below. >>> >>> On 2012/06/09, at 1:54, Fernando Lozano <fer...@lo...> wrote: >>> >>>> Hi Michael, >>>> >>>> Very interesting, but the docs states that it is "transparent" only for libpq clients. This means Java clients (using the type 4 JDBC driver) can't use PostgreSQL XC? >>> Documentation is wrong. We tested with many drivers like php, ruby, perl, jdbc, ecpg, etc. >>> And the only problems we saw was with odbc because it uses returning and ctid. The rest was working well. >>> Could you indicate in which page the error is located? >>>> >>>> Also, as far as I understand the docs, I need something external do implement failover if I connect to a database server which comes offline (JBoss AS HA Datasources comes to mind), and there's no balancer included. Am I right? >>> Yes you are right. There is a kind of load balancing between Datanodes and Coordinators by design thanks to the distributed nature of tables and the possibility to control read for replicated tables on specific nodes. However it might be preferable to have load balancing from something external. >>> >>> Regards, >>> >>> Michael >>>> >>>> >>>> []s, Fernando Lozano >>>> >>>>> Hi all, >>>>> >>>>> Postgres-XC, read&write-scalable multi-master symmetric cluster based on PostgreSQL, version 1.0.0 is released. >>>>> This project is seen as an open-source alternative to costly products such as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can naturally use all its technologies, which are enhaunced to have a shared-nothing multi-master PostgreSQL-based database cluster. >>>>> >>>>> This first stable version is based on PostgreSQL 9.1.4. All the patches in PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of June 2012). >>>>> This includes the security fix related to pg_crypto dated of 30th of May. >>>>> You can download the source tarball directly from here: >>>>> https://sourceforge.net/projects/postgres-xc/files/latest/download >>>>> This tarball contains all the HTML and man documentation. >>>>> >>>>> 30 bug fixes have been made since release of beta2, with some notable enhancements: >>>>> - Support for EXTENSION is fixed >>>>> - Stabilization of the use of slave nodes in cluster >>>>> - Fix of a bug related to read-only transactions, improving performance by 15%. >>>>> - Support of compilation for MacOSX >>>>> About the scalability of this release, Postgres-XC 1.0.0 scales to a factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 nodes using a benchmark called DBT-1. >>>>> >>>>> Compared to version Postgres-XC 0.9.7, the following features have been added: >>>>> - Fast query shipping (FQS), quick identification of expressions in a query that can be pushed down to remote nodes >>>>> - SERIAL types >>>>> - TABLESPACE >>>>> - Utility to clean up 2PC transactions in cluster (pgxc_clean) >>>>> - Utility for initialization of GTM (global transaction manager, utility called initgtm) >>>>> - Relation-size functions and locking functions >>>>> - Regression stabilization >>>>> >>>>> The documentation of 1.0, including release notes, is available here: >>>>> http://postgres-xc.sourceforge.net/docs/1_0/. >>>>> >>>>> The project can be followed on Source Forge: http://postgres-xc.sourceforge.net/. >>>>> And a couple of GIT repositories are used for development: >>>>> - SourceForge: http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary >>>>> - Github: https://github.com/postgres-xc/postgres-xc >>>>> >>>>> The core team is currently working in the addition of new features for the next major release including: >>>>> - Merge with PostgreSQL 9.2 >>>>> - Data redistribution functionality, changing table distribution in cluster with a simple ALTER TABLE >>>>> - New functionalities related to online node addition and deletion for a better user experience >>>>> - Triggers >>>>> - Planner improvements >>>>> - Global constraints. >>>>> The roadmap of the project is located here => http://postgres-xc.sourceforge.net/ in section Roadmap. >>>>> >>>>> The project is under the same license as PostgreSQL, now managed under a single entity called "Postgres-XC Development Group". >>>>> In order to keep in touch with the project, whose development follows the same model as PostgreSQL, you can register to the following mailing lists: >>>>> - pos...@li..., for general questions. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>>> - pos...@li.... hachers mailing list. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >>>>> >>>>> See you soon on the project mailing list, and have fun with this stable release. >>>>> -- >>>>> Michael Paquier >>>>> Member of core team of Postgres-XC, and Postgres-XC Development Group >>>> >>>> >>> >> >> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |
|
From: Michael P. <mic...@gm...> - 2012-06-11 12:27:22
|
On Mon, Jun 11, 2012 at 9:13 PM, Fernando Lozano <fer...@lo...>wrote: > Hi Michael, > > Found the offending text. It's in the README from many releases, including > 1.0.0: > > Postgres-XC is aiming to provide transparent access to the database, which > means one can use existing PostgreSQL application as is. For implementation > reason, > ***transparency level is limited to access via libpq libraries*** > and simple statements as found in the Architecture Document in the release > material. > > PHP, Perl and most users won't be bothered because those language drivers > use libpq, but Java developers use a pure-java JDBC driver which does not > uses libpq at all. > > This statement on the README may be understood as "there are changes to > libpq in postgresql-xc so you have to use our libpq. Other clients won't > work". > The point is that we haven't changed libpq at all. It is exactly the same as vanilla postgres. > > But as I understand you reply, I can use any libpq to access postgresql-xc > without problem. For example, a pgAdminIII binary for windows that I > already use for a plain PostgreSQL server should work out-of-the-box with > PostgreSQL-XC, or the rpm files from Debian Linux for a PHP app. And I > could also use other clients, not based on libpq, such as a JDBC driver > anda a .Net provider, right? > Yes everything should work. I played a couple of months ago and pgadmin was working correctly by connecting to Coordinator. Other drivers also should work normally. If they do not work, well it is a bug. As I told before there are only limitations with odbc, because it uses ctid and in XC ctid is not unique among nodes. Btw, I found that the incorrect file is in the README of each version folder in SourceForge. Thanks for pointing that out. I'll upload a modified version. -- Michael Paquier http://michael.otacoo.com |
|
From: Fernando L. <fer...@lo...> - 2012-06-11 12:13:49
|
Hi Michael, Found the offending text. It's in the README from many releases, including 1.0.0: Postgres-XC is aiming to provide transparent access to the database, which means one can use existing PostgreSQL application as is. For implementation reason, ***transparency level is limited to access via libpq libraries*** and simple statements as found in the Architecture Document in the release material. PHP, Perl and most users won't be bothered because those language drivers use libpq, but Java developers use a pure-java JDBC driver which does not uses libpq at all. This statement on the README may be understood as "there are changes to libpq in postgresql-xc so you have to use our libpq. Other clients won't work". But as I understand you reply, I can use any libpq to access postgresql-xc without problem. For example, a pgAdminIII binary for windows that I already use for a plain PostgreSQL server should work out-of-the-box with PostgreSQL-XC, or the rpm files from Debian Linux for a PHP app. And I could also use other clients, not based on libpq, such as a JDBC driver anda a .Net provider, right? []s, Fernando Lozano > Hi, > > I spent half an hour browsing the website, wiki and docs and could not > find where I read that postgresql-xc should be transparent to libpq > clients. Will keep looking later. > > > []s, Fernando Lozano > > >> Hi, >> >> You should avoid sending responses to Postgres announce mailing lists >> people are going to complain. Better to use the MLs dedicated to xc. >> Please find my answers below. >> >> On 2012/06/09, at 1:54, Fernando Lozano <fer...@lo... >> <mailto:fer...@lo...>> wrote: >> >>> Hi Michael, >>> >>> Very interesting, but the docs states that it is "transparent" only >>> for libpq clients. This means Java clients (using the type 4 JDBC >>> driver) can't use PostgreSQL XC? >> Documentation is wrong. We tested with many drivers like php, ruby, >> perl, jdbc, ecpg, etc. >> And the only problems we saw was with odbc because it uses returning >> and ctid. The rest was working well. >> Could you indicate in which page the error is located? >>> >>> Also, as far as I understand the docs, I need something external do >>> implement failover if I connect to a database server which comes >>> offline (JBoss AS HA Datasources comes to mind), and there's no >>> balancer included. Am I right? >> Yes you are right. There is a kind of load balancing between >> Datanodes and Coordinators by design thanks to the distributed nature >> of tables and the possibility to control read for replicated tables >> on specific nodes. However it might be preferable to have load >> balancing from something external. >> >> Regards, >> >> Michael >>> >>> >>> []s, Fernando Lozano >>> >>>> Hi all, >>>> >>>> Postgres-XC, read&write-scalable multi-master symmetric cluster >>>> based on PostgreSQL, version 1.0.0 is released. >>>> This project is seen as an open-source alternative to costly >>>> products such as OracleRAC. Postgres-XC is based on the code of >>>> PostgreSQL, so it can naturally use all its technologies, which are >>>> enhaunced to have a shared-nothing multi-master PostgreSQL-based >>>> database cluster. >>>> >>>> This first stable version is based on PostgreSQL 9.1.4. All the >>>> patches in PostgreSQL 9.1 stable branch have been merged up to >>>> commit 873d1c1 (1st of June 2012). >>>> This includes the security fix related to pg_crypto dated of 30th >>>> of May. >>>> You can download the source tarball directly from here: >>>> https://sourceforge.net/projects/postgres-xc/files/latest/download >>>> This tarball contains all the HTML and man documentation. >>>> >>>> 30 bug fixes have been made since release of beta2, with some >>>> notable enhancements: >>>> - Support for EXTENSION is fixed >>>> - Stabilization of the use of slave nodes in cluster >>>> - Fix of a bug related to read-only transactions, improving >>>> performance by 15%. >>>> - Support of compilation for MacOSX >>>> About the scalability of this release, Postgres-XC 1.0.0 scales to >>>> a factor of 3 when compared to a standalone server PostgreSQL 9.1.3 >>>> on 5 nodes using a benchmark called DBT-1. >>>> >>>> Compared to version Postgres-XC 0.9.7, the following features have >>>> been added: >>>> - Fast query shipping (FQS), quick identification of expressions in >>>> a query that can be pushed down to remote nodes >>>> - SERIAL types >>>> - TABLESPACE >>>> - Utility to clean up 2PC transactions in cluster (pgxc_clean) >>>> - Utility for initialization of GTM (global transaction manager, >>>> utility called initgtm) >>>> - Relation-size functions and locking functions >>>> - Regression stabilization >>>> >>>> The documentation of 1.0, including release notes, is available here: >>>> http://postgres-xc.sourceforge.net/docs/1_0/. >>>> >>>> The project can be followed on Source Forge: >>>> http://postgres-xc.sourceforge.net/. >>>> And a couple of GIT repositories are used for development: >>>> - SourceForge: >>>> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary >>>> - Github: https://github.com/postgres-xc/postgres-xc >>>> >>>> The core team is currently working in the addition of new features >>>> for the next major release including: >>>> - Merge with PostgreSQL 9.2 >>>> - Data redistribution functionality, changing table distribution in >>>> cluster with a simple ALTER TABLE >>>> - New functionalities related to online node addition and deletion >>>> for a better user experience >>>> - Triggers >>>> - Planner improvements >>>> - Global constraints. >>>> The roadmap of the project is located here => >>>> http://postgres-xc.sourceforge.net/ in section Roadmap. >>>> >>>> The project is under the same license as PostgreSQL, now managed >>>> under a single entity called "Postgres-XC Development Group". >>>> In order to keep in touch with the project, whose development >>>> follows the same model as PostgreSQL, you can register to the >>>> following mailing lists: >>>> - pos...@li... >>>> <mailto:pos...@li...>, for general >>>> questions. Registration can be done here: >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>> - pos...@li... >>>> <mailto:pos...@li...>. hachers >>>> mailing list. Registration can be done here: >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >>>> >>>> See you soon on the project mailing list, and have fun with this >>>> stable release. >>>> -- >>>> Michael Paquier >>>> Member of core team of Postgres-XC, and Postgres-XC Development Group >>> >>> > > |
|
From: Michael P. <mic...@gm...> - 2012-06-11 12:04:16
|
On Mon, Jun 11, 2012 at 9:02 PM, Fernando Lozano <fer...@lo...>wrote: > Hi, > > I spent half an hour browsing the website, wiki and docs and could not > find where I read that postgresql-xc should be transparent to libpq > clients. Will keep looking later. > Thanks. Please keep me updated if you find anything. Improving documentation is a nerver-ending task Regards, > > > []s, Fernando Lozano > > > Hi, > > You should avoid sending responses to Postgres announce mailing lists > people are going to complain. Better to use the MLs dedicated to xc. > Please find my answers below. > > On 2012/06/09, at 1:54, Fernando Lozano <fer...@lo...> wrote: > > Hi Michael, > > Very interesting, but the docs states that it is "transparent" only for > libpq clients. This means Java clients (using the type 4 JDBC driver) can't > use PostgreSQL XC? > > Documentation is wrong. We tested with many drivers like php, ruby, perl, > jdbc, ecpg, etc. > And the only problems we saw was with odbc because it uses returning and > ctid. The rest was working well. > Could you indicate in which page the error is located? > > > Also, as far as I understand the docs, I need something external do > implement failover if I connect to a database server which comes offline > (JBoss AS HA Datasources comes to mind), and there's no balancer included. > Am I right? > > Yes you are right. There is a kind of load balancing between Datanodes and > Coordinators by design thanks to the distributed nature of tables and the > possibility to control read for replicated tables on specific nodes. > However it might be preferable to have load balancing from something > external. > > Regards, > > Michael > > > > []s, Fernando Lozano > > Hi all, > > Postgres-XC, read&write-scalable multi-master symmetric cluster based on > PostgreSQL, version 1.0.0 is released. > This project is seen as an open-source alternative to costly products such > as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can > naturally use all its technologies, which are enhaunced to have a > shared-nothing multi-master PostgreSQL-based database cluster. > > This first stable version is based on PostgreSQL 9.1.4. All the patches in > PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of > June 2012). > This includes the security fix related to pg_crypto dated of 30th of May. > You can download the source tarball directly from here: > https://sourceforge.net/projects/postgres-xc/files/latest/download > This tarball contains all the HTML and man documentation. > > 30 bug fixes have been made since release of beta2, with some notable > enhancements: > - Support for EXTENSION is fixed > - Stabilization of the use of slave nodes in cluster > - Fix of a bug related to read-only transactions, improving performance by > 15%. > - Support of compilation for MacOSX > About the scalability of this release, Postgres-XC 1.0.0 scales to a > factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 > nodes using a benchmark called DBT-1. > > Compared to version Postgres-XC 0.9.7, the following features have been > added: > - Fast query shipping (FQS), quick identification of expressions in a > query that can be pushed down to remote nodes > - SERIAL types > - TABLESPACE > - Utility to clean up 2PC transactions in cluster (pgxc_clean) > - Utility for initialization of GTM (global transaction manager, utility > called initgtm) > - Relation-size functions and locking functions > - Regression stabilization > > The documentation of 1.0, including release notes, is available here: > http://postgres-xc.sourceforge.net/docs/1_0/. > > The project can be followed on Source Forge: > http://postgres-xc.sourceforge.net/. > And a couple of GIT repositories are used for development: > - SourceForge: > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary > - Github: https://github.com/postgres-xc/postgres-xc > > The core team is currently working in the addition of new features for the > next major release including: > - Merge with PostgreSQL 9.2 > - Data redistribution functionality, changing table distribution in > cluster with a simple ALTER TABLE > - New functionalities related to online node addition and deletion for a > better user experience > - Triggers > - Planner improvements > - Global constraints. > The roadmap of the project is located here => > http://postgres-xc.sourceforge.net/ in section Roadmap. > > The project is under the same license as PostgreSQL, now managed under a > single entity called "Postgres-XC Development Group". > In order to keep in touch with the project, whose development follows the > same model as PostgreSQL, you can register to the following mailing lists: > - pos...@li..., for general questions. > Registration can be done here: > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > - pos...@li.... hachers mailing list. > Registration can be done here: > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > See you soon on the project mailing list, and have fun with this stable > release. > -- > Michael Paquier > Member of core team of Postgres-XC, and Postgres-XC Development Group > > > > > > -- Michael Paquier http://michael.otacoo.com |
|
From: Fernando L. <fer...@lo...> - 2012-06-11 12:02:41
|
Hi, I spent half an hour browsing the website, wiki and docs and could not find where I read that postgresql-xc should be transparent to libpq clients. Will keep looking later. []s, Fernando Lozano > Hi, > > You should avoid sending responses to Postgres announce mailing lists > people are going to complain. Better to use the MLs dedicated to xc. > Please find my answers below. > > On 2012/06/09, at 1:54, Fernando Lozano <fer...@lo... > <mailto:fer...@lo...>> wrote: > >> Hi Michael, >> >> Very interesting, but the docs states that it is "transparent" only >> for libpq clients. This means Java clients (using the type 4 JDBC >> driver) can't use PostgreSQL XC? > Documentation is wrong. We tested with many drivers like php, ruby, > perl, jdbc, ecpg, etc. > And the only problems we saw was with odbc because it uses returning > and ctid. The rest was working well. > Could you indicate in which page the error is located? >> >> Also, as far as I understand the docs, I need something external do >> implement failover if I connect to a database server which comes >> offline (JBoss AS HA Datasources comes to mind), and there's no >> balancer included. Am I right? > Yes you are right. There is a kind of load balancing between Datanodes > and Coordinators by design thanks to the distributed nature of tables > and the possibility to control read for replicated tables on specific > nodes. However it might be preferable to have load balancing from > something external. > > Regards, > > Michael >> >> >> []s, Fernando Lozano >> >>> Hi all, >>> >>> Postgres-XC, read&write-scalable multi-master symmetric cluster >>> based on PostgreSQL, version 1.0.0 is released. >>> This project is seen as an open-source alternative to costly >>> products such as OracleRAC. Postgres-XC is based on the code of >>> PostgreSQL, so it can naturally use all its technologies, which are >>> enhaunced to have a shared-nothing multi-master PostgreSQL-based >>> database cluster. >>> >>> This first stable version is based on PostgreSQL 9.1.4. All the >>> patches in PostgreSQL 9.1 stable branch have been merged up to >>> commit 873d1c1 (1st of June 2012). >>> This includes the security fix related to pg_crypto dated of 30th of >>> May. >>> You can download the source tarball directly from here: >>> https://sourceforge.net/projects/postgres-xc/files/latest/download >>> This tarball contains all the HTML and man documentation. >>> >>> 30 bug fixes have been made since release of beta2, with some >>> notable enhancements: >>> - Support for EXTENSION is fixed >>> - Stabilization of the use of slave nodes in cluster >>> - Fix of a bug related to read-only transactions, improving >>> performance by 15%. >>> - Support of compilation for MacOSX >>> About the scalability of this release, Postgres-XC 1.0.0 scales to a >>> factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on >>> 5 nodes using a benchmark called DBT-1. >>> >>> Compared to version Postgres-XC 0.9.7, the following features have >>> been added: >>> - Fast query shipping (FQS), quick identification of expressions in >>> a query that can be pushed down to remote nodes >>> - SERIAL types >>> - TABLESPACE >>> - Utility to clean up 2PC transactions in cluster (pgxc_clean) >>> - Utility for initialization of GTM (global transaction manager, >>> utility called initgtm) >>> - Relation-size functions and locking functions >>> - Regression stabilization >>> >>> The documentation of 1.0, including release notes, is available here: >>> http://postgres-xc.sourceforge.net/docs/1_0/. >>> >>> The project can be followed on Source Forge: >>> http://postgres-xc.sourceforge.net/. >>> And a couple of GIT repositories are used for development: >>> - SourceForge: >>> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary >>> - Github: https://github.com/postgres-xc/postgres-xc >>> >>> The core team is currently working in the addition of new features >>> for the next major release including: >>> - Merge with PostgreSQL 9.2 >>> - Data redistribution functionality, changing table distribution in >>> cluster with a simple ALTER TABLE >>> - New functionalities related to online node addition and deletion >>> for a better user experience >>> - Triggers >>> - Planner improvements >>> - Global constraints. >>> The roadmap of the project is located here => >>> http://postgres-xc.sourceforge.net/ in section Roadmap. >>> >>> The project is under the same license as PostgreSQL, now managed >>> under a single entity called "Postgres-XC Development Group". >>> In order to keep in touch with the project, whose development >>> follows the same model as PostgreSQL, you can register to the >>> following mailing lists: >>> - pos...@li... >>> <mailto:pos...@li...>, for general >>> questions. Registration can be done here: >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> - pos...@li... >>> <mailto:pos...@li...>. hachers >>> mailing list. Registration can be done here: >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >>> >>> See you soon on the project mailing list, and have fun with this >>> stable release. >>> -- >>> Michael Paquier >>> Member of core team of Postgres-XC, and Postgres-XC Development Group >> >> |
|
From: Koichi S. <ko...@in...> - 2012-06-11 00:32:27
|
Hmmm... It's more interesting. --- Koichi On Sat, 9 Jun 2012 13:08:01 -0400 Mason <ma...@us...> wrote: > On Sat, Jun 9, 2012 at 5:40 AM, Michael Paquier > <mic...@gm...> wrote: > > Hi, > > > > I found an article while browsing the web comparing pgpool-ii, XC and > > postgres. OK, that's mostly pgpool but the latest paragraph is what caught > > my attention. > > It would be nice to get in touch with this guy, it doesn't look that he > > heard about the latest news of the project: release of 1.0. > > http://www.varnernet.com/~bryan/2012/05/29/i-love-postgresql-but-pgpool-ii-is-another-story/ > > > > At least the comment on pgpool-ii is kind of... interesting. > > I let see it yourself. > > > > Someone knows who this guy is? > > I replied about a week ago, but he either deleted my response or is > moderating comments. > > Mason > > > -- > > Michael Paquier > > http://michael.otacoo.com > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: Mason <ma...@us...> - 2012-06-09 17:08:08
|
On Sat, Jun 9, 2012 at 5:40 AM, Michael Paquier <mic...@gm...> wrote: > Hi, > > I found an article while browsing the web comparing pgpool-ii, XC and > postgres. OK, that's mostly pgpool but the latest paragraph is what caught > my attention. > It would be nice to get in touch with this guy, it doesn't look that he > heard about the latest news of the project: release of 1.0. > http://www.varnernet.com/~bryan/2012/05/29/i-love-postgresql-but-pgpool-ii-is-another-story/ > > At least the comment on pgpool-ii is kind of... interesting. > I let see it yourself. > > Someone knows who this guy is? I replied about a week ago, but he either deleted my response or is moderating comments. Mason > -- > Michael Paquier > http://michael.otacoo.com > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
43 messages has been excluded from this view by a project administrator.
