Menu
▾
▴
postgres-xc-general
|
From: seikath <se...@gm...> - 2013-03-26 14:16:53
|
Hello all, I have an XC setup of 4 AWS instances: ============================= instance: prod-xc-coord1 coordinator config at prod-xc-coord1 listen_addresses = '*' port = 5432 max_connections = 100 shared_buffers = 120MB max_prepared_transactions = 100 datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' lc_monetary = 'en_US.UTF-8' lc_numeric = 'en_US.UTF-8' lc_time = 'en_US.UTF-8' default_text_search_config = 'pg_catalog.english' pooler_port = 6667 min_pool_size = 1 max_pool_size = 100 max_coordinators = 16 max_datanodes = 16 gtm_host = '10.196.154.85' gtm_port = 6543 pgxc_node_name = 'coord1' enforce_two_phase_commit = on enable_fast_query_shipping = on enable_remotejoin = on enable_remotegroup = on datanode config at prod-xc-coord1 listen_addresses = '*' port = 6543 max_connections = 100 shared_buffers = 320MB max_prepared_transactions = 100 datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' lc_monetary = 'en_US.UTF-8' lc_numeric = 'en_US.UTF-8' lc_time = 'en_US.UTF-8' default_text_search_config = 'pg_catalog.english' max_coordinators = 16 max_datanodes = 16 gtm_host = '10.196.154.85' gtm_port = 6543 pgxc_node_name = 'datanode1' enforce_two_phase_commit = on enable_fast_query_shipping = on enable_remotejoin = on enable_remotegroup = on ============================= instance : prod-xc-coord2 coordinator config at prod-xc-coord2 listen_addresses = '*' port = 5432 max_connections = 100 superuser_reserved_connections = 3 shared_buffers = 120MB max_prepared_transactions = 100 datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' lc_monetary = 'en_US.UTF-8' lc_numeric = 'en_US.UTF-8' lc_time = 'en_US.UTF-8' default_text_search_config = 'pg_catalog.english' pooler_port = 6667 min_pool_size = 1 max_pool_size = 100 max_coordinators = 16 max_datanodes = 16 gtm_host = '10.196.154.85' gtm_port = 6543 pgxc_node_name = 'coord2' enforce_two_phase_commit = on enable_fast_query_shipping = on enable_remotejoin = on enable_remotegroup = on datanode config at prod-xc-coord2 listen_addresses = '*' port = 6543 max_connections = 100 shared_buffers = 320MB max_prepared_transactions = 100 datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' lc_monetary = 'en_US.UTF-8' lc_numeric = 'en_US.UTF-8' lc_time = 'en_US.UTF-8' default_text_search_config = 'pg_catalog.english' max_coordinators = 16 max_datanodes = 16 gtm_host = '10.196.154.85' gtm_port = 6543 pgxc_node_name = 'datanode2' enforce_two_phase_commit = on enable_fast_query_shipping = on enable_remotejoin = on enable_remotegroup = on ============================= instance prod-xc-gtm-proxy : IP 10.196.154.85 proxy config: nodename = 'one' listen_addresses = '*' port = 6543 gtm_host = '10.244.158.120' gtm_port = 5432 ============================= instance prod-xc-gtm : IP 10.244.158.120 gtm config nodename = 'one' listen_addresses = '*' port = 5432 ============================= the pg_hba,conf of both coordinator and data nodes at both prod-xc-coord1 and prod-xc-coord2 allows the other node to connect: ================================================= pg_hba,conf at prod-xc-coord01 IP 10.245.114.8 local all all trust host all all 127.0.0.1/32 trust host all all ::1/128 trust host all all 10.101.51.38/32 trust pg_hba,conf at prod-xc-coord02 IP 10.101.51.38 local all all trust host all all 127.0.0.1/32 trust host all all ::1/128 trust host all all 10.245.114.8/32 trust the connectivity is tested and confirmed. ================================================= initial nodes setup: prod-xc-coord01 postgres=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id -----------+-----------+-----------+--------------+----------------+------------------+------------ coord1 | C | 5432 | localhost | f | f | 1885696643 datanode1 | D | 6543 | localhost | t | t | 888802358 datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 prod-xc-coord02 postgres=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id -----------+-----------+-----------+--------------+----------------+------------------+------------- coord2 | C | 5432 | localhost | f | f | -1197102633 datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 datanode2 | D | 6543 | localhost | f | t | -905831925 after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. then tested and the node setup with one only primary node: prod-xc-coord02 postgres=# alter node datanode1 with (type = 'datanode', host = '10.245.114.8', port = 6543, primary=false,preferred=false); ALTER NODE postgres=# select pgxc_pool_reload(); pgxc_pool_reload ------------------ t (1 row) postgres=# select * from pgxc_node; node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id -----------+-----------+-----------+--------------+----------------+------------------+------------- coord2 | C | 5432 | localhost | f | f | -1197102633 datanode2 | D | 6543 | localhost | f | t | -905831925 datanode1 | D | 6543 | 10.245.114.8 | f | f | 888802358 (3 rows) the result is the same. I know I am missing something simple as a config or open port, but at the moment I cant figure out whats missing in the setup. In general our plan is to use loadbalancer in frond of several instances hosting one coordinator and one datanode. I apologize for the ugly paste, but I am not sure if that mail list support html formatting. Kind regards, Ivan |
|
From: Ashutosh B. <ash...@en...> - 2013-03-26 14:21:13
|
On Tue, Mar 26, 2013 at 7:46 PM, seikath <se...@gm...> wrote: > Hello all, > > I have an XC setup of 4 AWS instances: > > ============================= > instance: prod-xc-coord1 > > coordinator config at prod-xc-coord1 > listen_addresses = '*' > port = 5432 > max_connections = 100 > shared_buffers = 120MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > pooler_port = 6667 > min_pool_size = 1 > max_pool_size = 100 > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'coord1' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > datanode config at prod-xc-coord1 > listen_addresses = '*' > port = 6543 > max_connections = 100 > shared_buffers = 320MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'datanode1' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > > ============================= > instance : prod-xc-coord2 > > coordinator config at prod-xc-coord2 > listen_addresses = '*' > port = 5432 > max_connections = 100 > superuser_reserved_connections = 3 > shared_buffers = 120MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > pooler_port = 6667 > min_pool_size = 1 > max_pool_size = 100 > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'coord2' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > datanode config at prod-xc-coord2 > listen_addresses = '*' > port = 6543 > max_connections = 100 > shared_buffers = 320MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'datanode2' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > ============================= > instance prod-xc-gtm-proxy : IP 10.196.154.85 > > proxy config: > nodename = 'one' > listen_addresses = '*' > port = 6543 > gtm_host = '10.244.158.120' > gtm_port = 5432 > > ============================= > instance prod-xc-gtm : IP 10.244.158.120 > gtm config > nodename = 'one' > listen_addresses = '*' > port = 5432 > > > ============================= > > the pg_hba,conf of both coordinator and data nodes at both prod-xc-coord1 > and prod-xc-coord2 > allows the other node to connect: > ================================================= > pg_hba,conf at prod-xc-coord01 IP 10.245.114.8 > local all all trust > host all all 127.0.0.1/32 trust > host all all ::1/128 trust > host all all 10.101.51.38/32 trust > > pg_hba,conf at prod-xc-coord02 IP 10.101.51.38 > local all all trust > host all all 127.0.0.1/32 trust > host all all ::1/128 trust > host all all 10.245.114.8/32 trust > > the connectivity is tested and confirmed. > ================================================= > > initial nodes setup: > prod-xc-coord01 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------ > coord1 | C | 5432 | localhost | f | f > | 1885696643 > datanode1 | D | 6543 | localhost | t | t > | 888802358 > datanode2 | D | 6543 | 10.101.51.38 | f | f > | -905831925 > > prod-xc-coord02 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > coord2 | C | 5432 | localhost | f | f > | -1197102633 > datanode1 | D | 6543 | 10.245.114.8 | t | f > | 888802358 > datanode2 | D | 6543 | localhost | f | t > | -905831925 > > after that setup I was able to create tabases from the both coordinator > nodes, but each coordinator does not see the database created by the other > coordinator. > > > > then tested and the node setup with one only primary node: > prod-xc-coord02 > postgres=# alter node datanode1 with (type = 'datanode', host = > '10.245.114.8', port = 6543, primary=false,preferred=false); > ALTER NODE > postgres=# select pgxc_pool_reload(); > pgxc_pool_reload > ------------------ > t > (1 row) > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > coord2 | C | 5432 | localhost | f | f > | -1197102633 > datanode2 | D | 6543 | localhost | f | t > | -905831925 > datanode1 | D | 6543 | 10.245.114.8 | f | f > | 888802358 > (3 rows) > > the result is the same. > > I know I am missing something simple as a config or open port, but at the > moment I cant figure out whats missing in the setup. > > What are you trying to do here? You have set primary node for datanode1 to false, which is what the query result displays. Can you please elaborate what's going wrong? > In general our plan is to use loadbalancer in frond of several instances > hosting one coordinator and one datanode. > > I apologize for the ugly paste, but I am not sure if that mail list > support html formatting. > > Kind regards, > > Ivan > > > > > > > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > 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: seikath <se...@gm...> - 2013-03-26 14:31:18
|
Hello Ashutosh, My initial setup was datanode1 as primary on all coordinators. But the database created on coordinator1 was not visible by coordinator2 even it was populated at the both datanodes. So I tested with one primary datanode on one coordinator, hoping the GTM will know that and will distribute the info. Anyway, these are my firsts steps with XC, so I might did some simple config error .. I want to use the coordinators as a entry points for loadbalanced external SQL requests Kind regards, Ivan On 03/26/2013 03:21 PM, Ashutosh Bapat wrote: > > > On Tue, Mar 26, 2013 at 7:46 PM, seikath <se...@gm... <mailto:se...@gm...>> wrote: > > Hello all, > > I have an XC setup of 4 AWS instances: > > ============================= > instance: prod-xc-coord1 > > coordinator config at prod-xc-coord1 > listen_addresses = '*' > port = 5432 > max_connections = 100 > shared_buffers = 120MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > pooler_port = 6667 > min_pool_size = 1 > max_pool_size = 100 > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'coord1' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > datanode config at prod-xc-coord1 > listen_addresses = '*' > port = 6543 > max_connections = 100 > shared_buffers = 320MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'datanode1' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > > ============================= > instance : prod-xc-coord2 > > coordinator config at prod-xc-coord2 > listen_addresses = '*' > port = 5432 > max_connections = 100 > superuser_reserved_connections = 3 > shared_buffers = 120MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > pooler_port = 6667 > min_pool_size = 1 > max_pool_size = 100 > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'coord2' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > datanode config at prod-xc-coord2 > listen_addresses = '*' > port = 6543 > max_connections = 100 > shared_buffers = 320MB > max_prepared_transactions = 100 > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' > default_text_search_config = 'pg_catalog.english' > max_coordinators = 16 > max_datanodes = 16 > gtm_host = '10.196.154.85' > gtm_port = 6543 > pgxc_node_name = 'datanode2' > enforce_two_phase_commit = on > enable_fast_query_shipping = on > enable_remotejoin = on > enable_remotegroup = on > > ============================= > instance prod-xc-gtm-proxy : IP 10.196.154.85 > > proxy config: > nodename = 'one' > listen_addresses = '*' > port = 6543 > gtm_host = '10.244.158.120' > gtm_port = 5432 > > ============================= > instance prod-xc-gtm : IP 10.244.158.120 > gtm config > nodename = 'one' > listen_addresses = '*' > port = 5432 > > > ============================= > > the pg_hba,conf of both coordinator and data nodes at both prod-xc-coord1 and prod-xc-coord2 > allows the other node to connect: > ================================================= > pg_hba,conf at prod-xc-coord01 IP 10.245.114.8 > local all all trust > host all all 127.0.0.1/32 <http://127.0.0.1/32> trust > host all all ::1/128 trust > host all all 10.101.51.38/32 <http://10.101.51.38/32> trust > > pg_hba,conf at prod-xc-coord02 IP 10.101.51.38 > local all all trust > host all all 127.0.0.1/32 <http://127.0.0.1/32> trust > host all all ::1/128 trust > host all all 10.245.114.8/32 <http://10.245.114.8/32> trust > > the connectivity is tested and confirmed. > ================================================= > > initial nodes setup: > prod-xc-coord01 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > -----------+-----------+-----------+--------------+----------------+------------------+------------ > coord1 | C | 5432 | localhost | f | f | 1885696643 > datanode1 | D | 6543 | localhost | t | t | 888802358 > datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 > > prod-xc-coord02 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > -----------+-----------+-----------+--------------+----------------+------------------+------------- > coord2 | C | 5432 | localhost | f | f | -1197102633 > datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 > datanode2 | D | 6543 | localhost | f | t | -905831925 > > after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other > coordinator. > > > > then tested and the node setup with one only primary node: > prod-xc-coord02 > postgres=# alter node datanode1 with (type = 'datanode', host = '10.245.114.8', port = 6543, primary=false,preferred=false); > ALTER NODE > postgres=# select pgxc_pool_reload(); > pgxc_pool_reload > ------------------ > t > (1 row) > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > -----------+-----------+-----------+--------------+----------------+------------------+------------- > coord2 | C | 5432 | localhost | f | f | -1197102633 > datanode2 | D | 6543 | localhost | f | t | -905831925 > datanode1 | D | 6543 | 10.245.114.8 | f | f | 888802358 > (3 rows) > > the result is the same. > > I know I am missing something simple as a config or open port, but at the moment I cant figure out whats missing in the setup. > > > What are you trying to do here? You have set primary node for datanode1 to false, which is what the query result displays. Can you please elaborate what's > going wrong? > > In general our plan is to use loadbalancer in frond of several instances hosting one coordinator and one datanode. > > I apologize for the ugly paste, but I am not sure if that mail list support html formatting. > > Kind regards, > > Ivan > > > > > > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... <mailto: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...> - 2013-03-27 03:25:08
|
Hi Ivan, On Tue, Mar 26, 2013 at 8:01 PM, seikath <se...@gm...> wrote: > Hello Ashutosh, > > My initial setup was datanode1 as primary on all coordinators. > > But the database created on coordinator1 was not visible by coordinator2 > even it was populated at the both datanodes. > > Can you provide some more information? This looks like a bug. > So I tested with one primary datanode on one coordinator, hoping the GTM > will know that and will distribute the info. > Anyway, these are my firsts steps with XC, so I might did some simple > config error .. > > I want to use the coordinators as a entry points for loadbalanced external > SQL requests > > Kind regards, > > Ivan > > > On 03/26/2013 03:21 PM, Ashutosh Bapat wrote: > > > > On Tue, Mar 26, 2013 at 7:46 PM, seikath <se...@gm...> wrote: > >> Hello all, >> >> I have an XC setup of 4 AWS instances: >> >> ============================= >> instance: prod-xc-coord1 >> >> coordinator config at prod-xc-coord1 >> listen_addresses = '*' >> port = 5432 >> max_connections = 100 >> shared_buffers = 120MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> pooler_port = 6667 >> min_pool_size = 1 >> max_pool_size = 100 >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'coord1' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> datanode config at prod-xc-coord1 >> listen_addresses = '*' >> port = 6543 >> max_connections = 100 >> shared_buffers = 320MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'datanode1' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> >> ============================= >> instance : prod-xc-coord2 >> >> coordinator config at prod-xc-coord2 >> listen_addresses = '*' >> port = 5432 >> max_connections = 100 >> superuser_reserved_connections = 3 >> shared_buffers = 120MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> pooler_port = 6667 >> min_pool_size = 1 >> max_pool_size = 100 >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'coord2' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> datanode config at prod-xc-coord2 >> listen_addresses = '*' >> port = 6543 >> max_connections = 100 >> shared_buffers = 320MB >> max_prepared_transactions = 100 >> datestyle = 'iso, mdy' >> lc_messages = 'en_US.UTF-8' >> lc_monetary = 'en_US.UTF-8' >> lc_numeric = 'en_US.UTF-8' >> lc_time = 'en_US.UTF-8' >> default_text_search_config = 'pg_catalog.english' >> max_coordinators = 16 >> max_datanodes = 16 >> gtm_host = '10.196.154.85' >> gtm_port = 6543 >> pgxc_node_name = 'datanode2' >> enforce_two_phase_commit = on >> enable_fast_query_shipping = on >> enable_remotejoin = on >> enable_remotegroup = on >> >> ============================= >> instance prod-xc-gtm-proxy : IP 10.196.154.85 >> >> proxy config: >> nodename = 'one' >> listen_addresses = '*' >> port = 6543 >> gtm_host = '10.244.158.120' >> gtm_port = 5432 >> >> ============================= >> instance prod-xc-gtm : IP 10.244.158.120 >> gtm config >> nodename = 'one' >> listen_addresses = '*' >> port = 5432 >> >> >> ============================= >> >> the pg_hba,conf of both coordinator and data nodes at both prod-xc-coord1 >> and prod-xc-coord2 >> allows the other node to connect: >> ================================================= >> pg_hba,conf at prod-xc-coord01 IP 10.245.114.8 >> local all all trust >> host all all 127.0.0.1/32 trust >> host all all ::1/128 trust >> host all all 10.101.51.38/32 trust >> >> pg_hba,conf at prod-xc-coord02 IP 10.101.51.38 >> local all all trust >> host all all 127.0.0.1/32 trust >> host all all ::1/128 trust >> host all all 10.245.114.8/32 trust >> >> the connectivity is tested and confirmed. >> ================================================= >> >> initial nodes setup: >> prod-xc-coord01 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------ >> coord1 | C | 5432 | localhost | f | f >> | 1885696643 >> datanode1 | D | 6543 | localhost | t | t >> | 888802358 >> datanode2 | D | 6543 | 10.101.51.38 | f | f >> | -905831925 >> >> prod-xc-coord02 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f >> | -1197102633 >> datanode1 | D | 6543 | 10.245.114.8 | t | f >> | 888802358 >> datanode2 | D | 6543 | localhost | f | t >> | -905831925 >> >> after that setup I was able to create tabases from the both coordinator >> nodes, but each coordinator does not see the database created by the other >> coordinator. >> >> >> >> then tested and the node setup with one only primary node: >> prod-xc-coord02 >> postgres=# alter node datanode1 with (type = 'datanode', host = >> '10.245.114.8', port = 6543, primary=false,preferred=false); >> ALTER NODE >> postgres=# select pgxc_pool_reload(); >> pgxc_pool_reload >> ------------------ >> t >> (1 row) >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | >> nodeis_preferred | node_id >> >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f >> | -1197102633 >> datanode2 | D | 6543 | localhost | f | t >> | -905831925 >> datanode1 | D | 6543 | 10.245.114.8 | f | f >> | 888802358 >> (3 rows) >> >> the result is the same. >> >> I know I am missing something simple as a config or open port, but at the >> moment I cant figure out whats missing in the setup. >> >> > What are you trying to do here? You have set primary node for datanode1 to > false, which is what the query result displays. Can you please elaborate > what's going wrong? > > >> In general our plan is to use loadbalancer in frond of several instances >> hosting one coordinator and one datanode. >> >> I apologize for the ugly paste, but I am not sure if that mail list >> support html formatting. >> >> Kind regards, >> >> Ivan >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Own the Future-Intel® Level Up Game Demo Contest 2013 >> Rise to greatness in Intel's independent game demo contest. >> Compete for recognition, cash, and the chance to get your game >> on Steam. $5K grand prize plus 10 genre and skill prizes. >> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d >> _______________________________________________ >> 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 > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > 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: Nikhil S. <ni...@st...> - 2013-03-26 18:16:47
|
> prod-xc-coord01 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > -----------+-----------+-----------+--------------+----------------+------------------+------------ > coord1 | C | 5432 | localhost | f | f | 1885696643 > datanode1 | D | 6543 | localhost | t | t | 888802358 > datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 > > prod-xc-coord02 > postgres=# select * from pgxc_node; > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > -----------+-----------+-----------+--------------+----------------+------------------+------------- > coord2 | C | 5432 | localhost | f | f | -1197102633 > datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 > datanode2 | D | 6543 | localhost | f | t | -905831925 > > after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. > You need to add coord1 metadata on coord2 node and vice versa as well. Regards, Nikhils -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: seikath <se...@gm...> - 2013-03-26 19:44:13
|
Nikhil, thank you, that did the job. Whenever you have a chance to visit Barcelona, let me know, I owe you one :) Kind regards, Ivan On 03/26/2013 07:16 PM, Nikhil Sontakke wrote: >> prod-xc-coord01 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >> -----------+-----------+-----------+--------------+----------------+------------------+------------ >> coord1 | C | 5432 | localhost | f | f | 1885696643 >> datanode1 | D | 6543 | localhost | t | t | 888802358 >> datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 >> >> prod-xc-coord02 >> postgres=# select * from pgxc_node; >> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >> -----------+-----------+-----------+--------------+----------------+------------------+------------- >> coord2 | C | 5432 | localhost | f | f | -1197102633 >> datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 >> datanode2 | D | 6543 | localhost | f | t | -905831925 >> >> after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. >> > You need to add coord1 metadata on coord2 node and vice versa as well. > > Regards, > Nikhils |
|
From: Michael P. <mic...@gm...> - 2013-03-27 03:56:30
|
On Wed, Mar 27, 2013 at 4:44 AM, seikath <se...@gm...> wrote: > Whenever you have a chance to visit Barcelona, let me know, I owe you one > :) > Avoid to say that... I can answer really, really quickly, and my home country is close to yours. My country even lost a soccer match yesterday against yours... ;) -- Michael |
|
From: Nikhil S. <ni...@st...> - 2013-03-27 06:06:55
|
> Whenever you have a chance to visit Barcelona, let me know, I owe you one :) > Barcelona! Sure Ivan :) Regards, Nikhils > Kind regards, > > Ivan > > On 03/26/2013 07:16 PM, Nikhil Sontakke wrote: >>> prod-xc-coord01 >>> postgres=# select * from pgxc_node; >>> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >>> -----------+-----------+-----------+--------------+----------------+------------------+------------ >>> coord1 | C | 5432 | localhost | f | f | 1885696643 >>> datanode1 | D | 6543 | localhost | t | t | 888802358 >>> datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 >>> >>> prod-xc-coord02 >>> postgres=# select * from pgxc_node; >>> node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id >>> -----------+-----------+-----------+--------------+----------------+------------------+------------- >>> coord2 | C | 5432 | localhost | f | f | -1197102633 >>> datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 >>> datanode2 | D | 6543 | localhost | f | t | -905831925 >>> >>> after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other coordinator. >>> >> You need to add coord1 metadata on coord2 node and vice versa as well. >> >> Regards, >> Nikhils > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general -- StormDB - http://www.stormdb.com The Database Cloud |
|
From: Michael P. <mic...@gm...> - 2013-03-27 03:52:41
|
On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st...>wrote: > > prod-xc-coord01 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > > -----------+-----------+-----------+--------------+----------------+------------------+------------ > > coord1 | C | 5432 | localhost | f | f > | 1885696643 > > datanode1 | D | 6543 | localhost | t | t > | 888802358 > > datanode2 | D | 6543 | 10.101.51.38 | f | f > | -905831925 > > > > prod-xc-coord02 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | > nodeis_preferred | node_id > > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > > coord2 | C | 5432 | localhost | f | f > | -1197102633 > > datanode1 | D | 6543 | 10.245.114.8 | t | f > | 888802358 > > datanode2 | D | 6543 | localhost | f | t > | -905831925 > > > > after that setup I was able to create tabases from the both coordinator > nodes, but each coordinator does not see the database created by the other > coordinator. > > > > You need to add coord1 metadata on coord2 node and vice versa as well. > There are so many people making the same mistake and requesting help for similar stuff on this mailing list that it should be worth improving the documentation. -- Michael |
|
From: seikath <se...@gm...> - 2013-03-27 08:47:14
|
I was about to put a request for that, most of the available sources do not have that particular info, all of them mantion only the datanodes creation. About the Barcleona, well, I keep my word guys, whoever is in *B*arcelona and have some free time, ping me please. At Michael: Im not a /Spaniard/, but I do enjoy watching football ( Visca Barça !!! ) with friends , some beers and sharing ideas and experience .. :) In fact I do that with several friends of mine from SkySQL .. Cheers, and thank you all again. Ivan On 03/27/2013 04:52 AM, Michael Paquier wrote: > > > On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st... <mailto:ni...@st...>> wrote: > > > prod-xc-coord01 > > postgres=# select * from pgxc_node; > > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------ > > coord1 | C | 5432 | localhost | f | f | 1885696643 > > datanode1 | D | 6543 | localhost | t | t | 888802358 > > datanode2 | D | 6543 | 10.101.51.38 | f | f | -905831925 > > > > prod-xc-coord02 > > postgres=# select * from pgxc_node > > node_name | node_type | node_port | node_host | nodeis_primary | nodeis_preferred | node_id > > -----------+-----------+-----------+--------------+----------------+------------------+------------- > > coord2 | C | 5432 | localhost | f | f | -1197102633 > > datanode1 | D | 6543 | 10.245.114.8 | t | f | 888802358 > > datanode2 | D | 6543 | localhost | f | t | -905831925 > > > > after that setup I was able to create tabases from the both coordinator nodes, but each coordinator does not see the database created by the other > coordinator. > > > > You need to add coord1 metadata on coord2 node and vice versa as well. > > There are so many people making the same mistake and requesting help for similar stuff on this mailing list that it should be worth improving the documentation. > -- > Michael |
|
From: Koichi S. <koi...@gm...> - 2013-03-28 08:47:32
|
Does anybody has a suggestion where such info should be added? CREATE|ALTER NODE? Configuration? I'm afraid configuration section in the document consists of too many descriptions. Even though we put such info here, we may need some separate sections/materials to guide "how to configure XC". Best; ---------- Koichi Suzuki 2013/3/27 seikath <se...@gm...>: > I was about to put a request for that, most of the available sources do not > have that particular info, all of them mantion only the datanodes creation. > > About the Barcleona, well, I keep my word guys, whoever is in Barcelona and > have some free time, ping me please. > > At Michael: Im not a Spaniard, but I do enjoy watching football ( Visca > Barça !!! ) with friends , some beers and sharing ideas and experience .. :) > > In fact I do that with several friends of mine from SkySQL .. > > Cheers, and thank you all again. > > Ivan > > On 03/27/2013 04:52 AM, Michael Paquier wrote: > > > > On Wed, Mar 27, 2013 at 3:16 AM, Nikhil Sontakke <ni...@st...> > wrote: >> >> > prod-xc-coord01 >> > postgres=# select * from pgxc_node; >> > node_name | node_type | node_port | node_host | nodeis_primary | >> > nodeis_preferred | node_id >> > >> > -----------+-----------+-----------+--------------+----------------+------------------+------------ >> > coord1 | C | 5432 | localhost | f | f >> > | 1885696643 >> > datanode1 | D | 6543 | localhost | t | t >> > | 888802358 >> > datanode2 | D | 6543 | 10.101.51.38 | f | f >> > | -905831925 >> > >> > prod-xc-coord02 >> > postgres=# select * from pgxc_node >> > node_name | node_type | node_port | node_host | nodeis_primary | >> > nodeis_preferred | node_id >> > >> > -----------+-----------+-----------+--------------+----------------+------------------+------------- >> > coord2 | C | 5432 | localhost | f | f >> > | -1197102633 >> > datanode1 | D | 6543 | 10.245.114.8 | t | f >> > | 888802358 >> > datanode2 | D | 6543 | localhost | f | t >> > | -905831925 >> > >> > after that setup I was able to create tabases from the both coordinator >> > nodes, but each coordinator does not see the database created by the other >> > coordinator. >> > >> >> You need to add coord1 metadata on coord2 node and vice versa as well. > > There are so many people making the same mistake and requesting help for > similar stuff on this mailing list that it should be worth improving the > documentation. > -- > Michael > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: seikath <se...@gm...> - 2013-04-05 09:17:04
|
Hello guys, PostgresSQL released patch due to http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 More info here: http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ Should we expect new release of PGXC ? Kind regards, Ivan |
|
From: Ashutosh B. <ash...@en...> - 2013-04-05 10:07:38
|
I think we should just pull PG stable branches with this fix to the corresponding XC stable branches (there is only one there). On Fri, Apr 5, 2013 at 3:31 PM, Andrei Martsinchyk < and...@gm...> wrote: > Just in case, the same for REL1_0_STABLE > > > 2013/4/5 Andrei Martsinchyk <and...@gm...> > >> Please find attached ported patch. >> >> >> >> >> 2013/4/5 seikath <se...@gm...> >> >>> Hello guys, >>> >>> PostgresSQL released patch due to >>> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 >>> >>> More info here: >>> http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ >>> >>> Should we expect new release of PGXC ? >>> >>> Kind regards, >>> >>> Ivan >>> >>> >>> ------------------------------------------------------------------------------ >>> Minimize network downtime and maximize team effectiveness. >>> Reduce network management and security costs.Learn how to hire >>> the most talented Cisco Certified professionals. Visit the >>> Employer Resources Portal >>> http://www.cisco.com/web/learning/employer_resources/index.html >>> _______________________________________________ >>> Postgres-xc-general mailing list >>> Pos...@li... >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >> >> >> >> -- >> Andrei Martsinchyk >> >> StormDB - http://www.stormdb.com >> The Database Cloud >> >> > > > -- > Andrei Martsinchyk > > StormDB - http://www.stormdb.com > The Database Cloud > > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > 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: Andrei M. <and...@gm...> - 2013-04-05 10:13:01
|
Sure, but patches are needed for current users. The vulnerability is critical, and it is recommended to upgrade as soon as possible. 2013/4/5 Ashutosh Bapat <ash...@en...> > I think we should just pull PG stable branches with this fix to the > corresponding XC stable branches (there is only one there). > > > On Fri, Apr 5, 2013 at 3:31 PM, Andrei Martsinchyk < > and...@gm...> wrote: > >> Just in case, the same for REL1_0_STABLE >> >> >> 2013/4/5 Andrei Martsinchyk <and...@gm...> >> >>> Please find attached ported patch. >>> >>> >>> >>> >>> 2013/4/5 seikath <se...@gm...> >>> >>>> Hello guys, >>>> >>>> PostgresSQL released patch due to >>>> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 >>>> >>>> More info here: >>>> http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ >>>> >>>> Should we expect new release of PGXC ? >>>> >>>> Kind regards, >>>> >>>> Ivan >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Minimize network downtime and maximize team effectiveness. >>>> Reduce network management and security costs.Learn how to hire >>>> the most talented Cisco Certified professionals. Visit the >>>> Employer Resources Portal >>>> http://www.cisco.com/web/learning/employer_resources/index.html >>>> _______________________________________________ >>>> Postgres-xc-general mailing list >>>> Pos...@li... >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>> >>> >>> >>> >>> -- >>> Andrei Martsinchyk >>> >>> StormDB - http://www.stormdb.com >>> The Database Cloud >>> >>> >> >> >> -- >> Andrei Martsinchyk >> >> StormDB - http://www.stormdb.com >> The Database Cloud >> >> >> >> ------------------------------------------------------------------------------ >> Minimize network downtime and maximize team effectiveness. >> Reduce network management and security costs.Learn how to hire >> the most talented Cisco Certified professionals. Visit the >> Employer Resources Portal >> http://www.cisco.com/web/learning/employer_resources/index.html >> _______________________________________________ >> 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 > -- Andrei Martsinchyk StormDB - http://www.stormdb.com The Database Cloud |
|
From: Michael P. <mic...@gm...> - 2013-04-05 11:38:16
|
On Fri, Apr 5, 2013 at 7:12 PM, Andrei Martsinchyk < and...@gm...> wrote: > Sure, but patches are needed for current users. > The vulnerability is critical, and it is recommended to upgrade as soon as > possible. > It is. But I agree with Ashutosh and a merge with stable branches should be done instead of applying a single patch. -- Michael |
|
From: Mason S. <ma...@st...> - 2013-04-05 21:41:41
|
On Fri, Apr 5, 2013 at 6:12 AM, Andrei Martsinchyk < and...@gm...> wrote: > Sure, but patches are needed for current users. > The vulnerability is critical, and it is recommended to upgrade as soon as > possible. > Thanks for submitting and responding so quickly to Ivan, Andrei. -- Mason Sharp StormDB - http://www.stormdb.com The Database Cloud Postgres-XC Support and Services |
|
From: Koichi S. <koi...@gm...> - 2013-04-07 14:32:10
|
Yes, we're planning 1.1 by the end of this June, with 9.2.4. I didn't have a plan to make 1,0.3 with 9.1.9. If there's enough requirement, we may have to consider to have it. Regards; ---------- Koichi Suzuki 2013/4/5 seikath <se...@gm...> > Hello guys, > > PostgresSQL released patch due to > http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 > > More info here: > http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ > > Should we expect new release of PGXC ? > > Kind regards, > > Ivan > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: seikath <se...@gm...> - 2013-04-08 06:06:23
|
Thank you Koichi, We moved to the git version with the security patch applied. Kind regards, Ivan Koichi Suzuki <koi...@gm...> wrote: >Yes, we're planning 1.1 by the end of this June, with 9.2.4. I didn't >have a plan to make 1,0.3 with 9.1.9. If there's enough requirement, >we >may have to consider to have it. > >Regards; >---------- >Koichi Suzuki > > >2013/4/5 seikath <se...@gm...> > >> Hello guys, >> >> PostgresSQL released patch due to >> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 >> >> More info here: >> http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ >> >> Should we expect new release of PGXC ? >> >> Kind regards, >> >> Ivan >> >> >> >------------------------------------------------------------------------------ >> Minimize network downtime and maximize team effectiveness. >> Reduce network management and security costs.Learn how to hire >> the most talented Cisco Certified professionals. Visit the >> Employer Resources Portal >> http://www.cisco.com/web/learning/employer_resources/index.html >> _______________________________________________ >> Postgres-xc-general mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
|
From: Koichi S. <koi...@gm...> - 2013-04-08 08:43:30
|
Hi! Are you planning to use 923merge branch? It is a work branch to keep our work. As Pavan pointed out, we made a serious mistake to apply stable blanch patch of PG to our master branch. It is very dangerous to keep our master consistent with PG master. The following step will be as follows: When we freeze a feature for 1.1, we will create a branch REL1_1_STABLE. 9.2.3 (and 9.2.4) merge will be done there. After the work, 923merge branch will be deleted. After REL1_1_STABLE is created, then all the current PG master commits will be merged with our master. This is not critical so we may schedule this work after 9.3 is out (at least 9.3 beta is out). So I'd advice to keep using master or REL1_0_STABLE branch whose lifetime is much longer. Best; ---------- Koichi Suzuki 2013/4/8 seikath <se...@gm...> > Thank you Koichi, > > We moved to the git version with the security patch applied. > > Kind regards, > > Ivan > > > Koichi Suzuki <koi...@gm...> wrote: >> >> Yes, we're planning 1.1 by the end of this June, with 9.2.4. I didn't >> have a plan to make 1,0.3 with 9.1.9. If there's enough requirement, we >> may have to consider to have it. >> >> Regards; >> ---------- >> Koichi Suzuki >> >> >> 2013/4/5 seikath <se...@gm...> >> >>> Hello guys, >>> >>> PostgresSQL released patch due to >>> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 >>> >>> More info here: >>> http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ >>> >>> Should we expect new release of PGXC ? >>> >>> Kind regards, >>> >>> Ivan >>> >>> >>> ------------------------------------------------------------------------------ >>> Minimize network downtime and maximize team effectiveness. >>> Reduce network management and security costs.Learn how to hire >>> the most talented Cisco Certified professionals. Visit the >>> Employer Resources Portal >>> http://www.cisco.com/web/learning/employer_resources/index.html >>> _______________________________________________ >>> Postgres-xc-general mailing list >>> Pos...@li... >>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>> >> >> > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > |
|
From: seikath <se...@gm...> - 2013-04-08 10:15:12
|
Thank you Koichi, I will revert back to stable, and will wait for.. June ! KInd regards, Ivan On 04/08/2013 10:43 AM, Koichi Suzuki wrote: > Hi! > > Are you planning to use 923merge branch? It is a work branch to keep our work. As Pavan pointed out, we made a serious mistake to apply stable blanch > patch of PG to our master branch. It is very dangerous to keep our master consistent with PG master. > > The following step will be as follows: > > When we freeze a feature for 1.1, we will create a branch REL1_1_STABLE. 9.2.3 (and 9.2.4) merge will be done there. After the work, 923merge branch will > be deleted. > > After REL1_1_STABLE is created, then all the current PG master commits will be merged with our master. This is not critical so we may schedule this work after > 9.3 is out (at least 9.3 beta is out). > > So I'd advice to keep using master or REL1_0_STABLE branch whose lifetime is much longer. > > Best; > > ---------- > Koichi Suzuki > > > 2013/4/8 seikath <se...@gm... <mailto:se...@gm...>> > > Thank you Koichi, > > We moved to the git version with the security patch applied. > > Kind regards, > > Ivan > > > Koichi Suzuki <koi...@gm... <mailto:koi...@gm...>> wrote: > > Yes, we're planning 1.1 by the end of this June, with 9.2.4. I didn't have a plan to make 1,0.3 with 9.1.9. If there's enough requirement, we may > have to consider to have it. > > Regards; > ---------- > Koichi Suzuki > > > 2013/4/5 seikath <se...@gm... <mailto:se...@gm...>> > > Hello guys, > > PostgresSQL released patch due to http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1899 > > More info here: http://www.theregister.co.uk/2013/04/04/postgresql_urgent_patch/ > > Should we expect new release of PGXC ? > > Kind regards, > > Ivan > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X