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: Ashutosh B. <ash...@en...> - 2013-04-12 03:20:02
|
This is interesting. I have been pondering over this. Can you please share some more details? On Thu, Apr 11, 2013 at 12:25 PM, Mason Sharp <mas...@gm...> wrote: > I will be presenting on Monday April 15th in Philadelphia at the Philly > PUG about using Postgres-XC as a key-value store. > > I will discuss hstore, XML and JSON, and include performance comparisons > to MongoDB. > > More information can be found here: > > http://www.phlpug.org/events/112128082/?eventId=112128082&action=detail > > Thanks, > > Mason Sharp > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > postgres-xc-announce mailing list > pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-announce > > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Koichi S. <ko...@in...> - 2013-04-12 01:03:39
|
This is published in January and Marcos Rodriguez Gomez posted a link to LinkedIn. On Fri, 12 Apr 2013 10:02:38 +0900 Koichi Suzuki <ko...@in...> wrote: > Hello; > > Ashutosh's article is now on linux for you site. > http://www.linuxforu.com/2012/01/postgres-xc-database-clustering-solution/ > > Thanks Ashutosh for the work. > > Enjoy everybody. > --- > Koichi Suzuki > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
|
From: Koichi S. <ko...@in...> - 2013-04-12 01:01:11
|
Hello; Ashutosh's article is now on linux for you site. http://www.linuxforu.com/2012/01/postgres-xc-database-clustering-solution/ Thanks Ashutosh for the work. Enjoy everybody. --- Koichi Suzuki |
|
From: Koichi S. <ko...@in...> - 2013-04-12 00:52:29
|
On Thu, 11 Apr 2013 18:07:13 +0900 Michael Paquier <mic...@gm...> wrote: > On Thu, Apr 11, 2013 at 4:22 PM, Theodotos Andreou <th...@ub...>wrote: > > > On 04/11/2013 04:05 AM, Hitoshi HEMMI wrote: > > > Hi Theodotos, > > > > > >> This is great! Are these RA open/freely available? Download Links? > > >> Maybe some guide/documentation? > > > > > > We use following RA. > > > > > https://github.com/t-matsuo/resource-agents/blob/7bf4daf29ec6d2e0aed4cf4b39a53118c2986a5a/heartbeat/pgsql > > > > > > This is for PostgreSQL but works fine for PGXC coordinator and > > > datanode without modification. > > > This is not for gtm/gtm-proxy. > > > > > > Hitoshi > > > > > > > Thanks Hitoshi! I will use this for coordinators and datanodes and > > pgxc_ctl for gtm. AFAIK there is no need for gtm_proxy failover, right? > > > Does pgxc_ctl provide failover and monitoring of GTM? > I thought it was only used for cluster set up... Yes it does. https://github.com/koichi-szk/PGXC-Tools/blob/master/pgxc_ctl/manual.txt gives bash-version manual, most of the features are in C-version as well. C-version will come with additional features as: 1) Add slave on the fly, 2) Add master on the fly (depends upon Abbas's node addition/removal), 3) Add gtm proxy on the fly. Please understand that pgxc_ctl is not "automatic" failover system. This feature will be available when it is integrated with HA middleware. I believe NTT people are developing such feature as general RA for pacemaker/heartbeat and I expect this will run with corosync as well. A couple of bash-version features depend upon direct support by bash and are not imported to C-version, although it has some alternatives. Regards; --- Koichi > -- > Michael |
|
From: Michael P. <mic...@gm...> - 2013-04-11 09:07:24
|
On Thu, Apr 11, 2013 at 4:22 PM, Theodotos Andreou <th...@ub...>wrote: > On 04/11/2013 04:05 AM, Hitoshi HEMMI wrote: > > Hi Theodotos, > > > >> This is great! Are these RA open/freely available? Download Links? > >> Maybe some guide/documentation? > > > > We use following RA. > > > https://github.com/t-matsuo/resource-agents/blob/7bf4daf29ec6d2e0aed4cf4b39a53118c2986a5a/heartbeat/pgsql > > > > This is for PostgreSQL but works fine for PGXC coordinator and > > datanode without modification. > > This is not for gtm/gtm-proxy. > > > > Hitoshi > > > > Thanks Hitoshi! I will use this for coordinators and datanodes and > pgxc_ctl for gtm. AFAIK there is no need for gtm_proxy failover, right? > Does pgxc_ctl provide failover and monitoring of GTM? I thought it was only used for cluster set up... -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-04-11 07:26:26
|
Wonderful! It is another are for XC. As I've just announced, we're going to have XC-Day at Ottawa, May 21st Tuesday, just after the cluster summit. I'd like to share your presentation and feedback from the audience there. ---------- Koichi Suzuki 2013/4/11 Mason Sharp <mas...@gm...> > I will be presenting on Monday April 15th in Philadelphia at the Philly > PUG about using Postgres-XC as a key-value store. > > I will discuss hstore, XML and JSON, and include performance comparisons > to MongoDB. > > More information can be found here: > > http://www.phlpug.org/events/112128082/?eventId=112128082&action=detail > > Thanks, > > Mason Sharp > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > postgres-xc-announce mailing list > pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-announce > > |
|
From: Theodotos A. <th...@ub...> - 2013-04-11 07:22:56
|
On 04/11/2013 04:05 AM, Hitoshi HEMMI wrote: > Hi Theodotos, > >> This is great! Are these RA open/freely available? Download Links? >> Maybe some guide/documentation? > > We use following RA. > https://github.com/t-matsuo/resource-agents/blob/7bf4daf29ec6d2e0aed4cf4b39a53118c2986a5a/heartbeat/pgsql > > This is for PostgreSQL but works fine for PGXC coordinator and > datanode without modification. > This is not for gtm/gtm-proxy. > > Hitoshi > Thanks Hitoshi! I will use this for coordinators and datanodes and pgxc_ctl for gtm. AFAIK there is no need for gtm_proxy failover, right? > > Theodotos Andreou さんは書きました: >> On 04/08/2013 06:52 AM, Nikhil Sontakke wrote: >>> Hi Theodotos, >>> >>>> Automatic monitoring and failover has not been provided yet. As >>>> Michael >>>> suggested, yes it's up to you at present. Sakata-san at NTT >>>> announced that >>>> they're developing XC RA for pacemaker/heartbeat (I hope it runs with >>>> Corosync too). >>>> >>> Yes, resource agents for pacemaker/corosync indeed work quite well for >>> XC HA. And yeah using heartbeat or corosync should be equivalent >>> mostly. >>> >>> We have indeed written custom agents for datanode and GTM monitoring >>> and HA using Corosync/Pacemaker and they work pretty well. >>> >>> Regards, >>> Nikhils >> This is great! Are these RA open/freely available? Download Links? >> Maybe some guide/documentation? >> >> ------------------------------------------------------------------------------ >> >> 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: Mason S. <mas...@gm...> - 2013-04-11 06:55:27
|
I will be presenting on Monday April 15th in Philadelphia at the Philly PUG about using Postgres-XC as a key-value store. I will discuss hstore, XML and JSON, and include performance comparisons to MongoDB. More information can be found here: http://www.phlpug.org/events/112128082/?eventId=112128082&action=detail Thanks, Mason Sharp |
|
From: Koichi S. <koi...@gm...> - 2013-04-11 05:43:59
|
Hi, PG-XCers; Postgres-XC is going to have its first user/developer meeting after the cluster summit. Information is as follows: When: May 21st, Tuesday, 3PM to 6PM. Where: University of Ottawa. Room TBD. Agenda: * Topics in Version 1.1 * Roadmap toward version 1.2 and beyond * Development Issues * Experiences Also, further discussion could be held on Wednesday, 22nd and/or Saturday, 25th. Details will be determined on Tuesday. Information will be found at https://wiki.postgresql.org/wiki/PgCon2013CanadaClusterSummit#PostgresXC_Summit I do hope you can join. Please feel free to register yourself and add our topics to discuss. If you have difficulty to do it. please mail to me. Thank you very much; ---------- Koichi Suzuki |
|
From: Hitoshi H. <hem...@la...> - 2013-04-11 01:06:00
|
Hi Theodotos, > This is great! Are these RA open/freely available? Download Links? Maybe > some guide/documentation? > We use following RA. https://github.com/t-matsuo/resource-agents/blob/7bf4daf29ec6d2e0aed4cf4b39a53118c2986a5a/heartbeat/pgsql This is for PostgreSQL but works fine for PGXC coordinator and datanode without modification. This is not for gtm/gtm-proxy. Hitoshi Theodotos Andreou さんは書きました: > On 04/08/2013 06:52 AM, Nikhil Sontakke wrote: > >> Hi Theodotos, >> >> >>> Automatic monitoring and failover has not been provided yet. As Michael >>> suggested, yes it's up to you at present. Sakata-san at NTT announced that >>> they're developing XC RA for pacemaker/heartbeat (I hope it runs with >>> Corosync too). >>> >>> >> Yes, resource agents for pacemaker/corosync indeed work quite well for >> XC HA. And yeah using heartbeat or corosync should be equivalent >> mostly. >> >> We have indeed written custom agents for datanode and GTM monitoring >> and HA using Corosync/Pacemaker and they work pretty well. >> >> Regards, >> Nikhils >> > This is great! Are these RA open/freely available? Download Links? Maybe > some guide/documentation? > > ------------------------------------------------------------------------------ > 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 > > -- Hitoshi HEMMI NTT Open Source Software Center hem...@la... Tel:(03)5860-5115 Fax:(03)5463-5490 |
|
From: Ashutosh B. <ash...@en...> - 2013-04-10 04:21:50
|
This looks strange. We run DBT-1 with multiple coordinators, where we open more than 10 connections, and don't see this phenomenon. Is there some load balancer or some tool sitting between coordinators and application? On Wed, Apr 10, 2013 at 1:32 AM, Arni Sumarlidason < Arn...@md...> wrote: > Mr. Bapat,**** > > ** ** > > Sorry for the slow response, I have been sick.**** > > ** ** > > I can open five connections to a coordinator, upon the sixth connection > all connections to any coordinator are dropped. I thought this might have > to do with the connection max specified in postgresql.conf, I adjusted it, > same results. No actions are necessary to recover from the crash, just open > a new connection.**** > > ** ** > > *From:* Ashutosh Bapat [mailto:ash...@en...] > *Sent:* Saturday, April 06, 2013 12:19 AM > > *To:* Arni Sumarlidason > *Cc:* pos...@li... > *Subject:* Re: [Postgres-xc-general] Heavy update utilization**** > > ** ** > > Can you please elaborate more on what kind of cascade failure you are > seeing? What are the symptoms? Is it crash? How bad it is? Does it affect > only the running transaction or entire systems needing reboot or needs data > clusters to be rebuilt?**** > > ** ** > > On Fri, Apr 5, 2013 at 7:12 PM, Arni Sumarlidason < > Arn...@md...> wrote:**** > > Does that also explain the cascade failure?**** > > **** > > Is there a cursor limit per coordinator?**** > > **** > > *From:* Ashutosh Bapat [mailto:ash...@en...] > *Sent:* Friday, April 05, 2013 1:37 AM > *To:* Arni Sumarlidason > *Cc:* pos...@li... > *Subject:* Re: [Postgres-xc-general] Heavy update utilization**** > > **** > > Inheritance is a problem here. Otherwise, we try to send DMLs involving a > single table directly to the datanode, without any planning at coordinator. > Unfortunately in this case since inheritance is involved, is row is > modified first on coordinator and then changed at the datanode.**** > > If you are going to use inheritance a lot, may be you want to take up > optimizations for inheritance cases (this is in the context of other > thread, where you have asked for a todo list.)**** > > **** > > On Fri, Apr 5, 2013 at 10:18 AM, Arni Sumarlidason < > Arn...@md...> wrote:**** > > Schema same as before, we left our schema inherited because we don't want > to reload our data when support is pushed out. **** > > **** > > Think inheritance is also causing this issue as well?**** > > **** > > Statement: Update table set col = "stuff" where Id = 447938**** > > **** > > Also might be worth mentioning we are using psycopg2 python connector. *** > * > > **** > > Thank you for your advice. > > Sent from my iPhone**** > > > On Apr 4, 2013, at 11:57 PM, "Ashutosh Bapat" < > ash...@en...> wrote:**** > > Can you please post your update query here with all the relevant > definitions like table schema etc.?**** > > **** > > On Fri, Apr 5, 2013 at 3:15 AM, Arni Sumarlidason < > Arn...@md...> wrote:**** > > General,**** > > **** > > We had a problem doing updates on our database today, it seems like > updates are a pretty heavy operation for the coordinator. They tack our > machines at 60-70% utilization[1] with 5 update cursors, and for reasons > unknown a 6th connection causes a cascade failure across all > coordinators. **** > > **** > > **** > > Do you know what would cause this?**** > > **** > > [1]**** > > http://www.sumarlidason.com/perm/130404/load8.PNG<https://console.mxlogic.com/redir/?zC763hOYqejhOrv7cIcECzAQsCM0l6Rtyv93qlxO-bv5n4mrInoM-KEfs5wo4zt-psLuZXTLsTsTJ2rsWQ9YgRrpwHUj-aQpkZ0xOVIs-eodEIKfEII9ILCTXCMnWhEwdbomHip6fQbxZyV7Uv7jPiWq80L-CiNEwrmgSvCy1KszV2CPBm1KvxYY1NJ4SOrpop73zhO-Ur3Fk-amvt>- Four machines at bottom of screen are coordinators, which correspond to > the thick utilization in the graph.**** > > **** > > > > ------------------------------------------------------------------------------ > 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<https://console.mxlogic.com/redir/?zC763hOYqejhOrv7cIcECzAQsCM0lFkJnBY05x_X64E4sZlo-FrUyIvFlKdLFw5Y3zt-psLuZXTLsTsTJ2rsWQ9YgRrpwHUj-aQpkZ0xOVIs-eodEIKfEII9ILCTXCMnWhEwdbomHip6fQbxZyV7Uv7jPiWq80L-CiNEwrmgSvCy1KszV2CPBm1KvxYY1NJcSOrpop73zhO-UrlC3O> > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general<https://console.mxlogic.com/redir/?2eosod7bNEVd79JYsOMOyqejhOr9PCJhbcfBiteFlKdLt00_MdM-l9QM-l9OwXn5GQChzZ2UvoKh-7NQYTvCnbTLuZXTdTdXgCTeJ2v4dmSoa-4_yJ6lfg8sKr7fzC3qbbzWbb2rbVJ-VI5-Aq83iS5GQChzZ2UvoKh-7NQYQKCy0b_FAIq86RAdDVEwrD8-gFIVlwrDUvf0srpdICSm6hMUQsLK6XlrO> > **** > > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company**** > > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company**** > > > > > -- > Best Wishes, > Ashutosh Bapat > EntepriseDB Corporation > The Enterprise Postgres Company**** > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Arni S. <Arn...@md...> - 2013-04-09 20:02:31
|
Mr. Bapat, Sorry for the slow response, I have been sick. I can open five connections to a coordinator, upon the sixth connection all connections to any coordinator are dropped. I thought this might have to do with the connection max specified in postgresql.conf, I adjusted it, same results. No actions are necessary to recover from the crash, just open a new connection. From: Ashutosh Bapat [mailto:ash...@en...] Sent: Saturday, April 06, 2013 12:19 AM To: Arni Sumarlidason Cc: pos...@li... Subject: Re: [Postgres-xc-general] Heavy update utilization Can you please elaborate more on what kind of cascade failure you are seeing? What are the symptoms? Is it crash? How bad it is? Does it affect only the running transaction or entire systems needing reboot or needs data clusters to be rebuilt? On Fri, Apr 5, 2013 at 7:12 PM, Arni Sumarlidason <Arn...@md...<mailto:Arn...@md...>> wrote: Does that also explain the cascade failure? Is there a cursor limit per coordinator? From: Ashutosh Bapat [mailto:ash...@en...<mailto:ash...@en...>] Sent: Friday, April 05, 2013 1:37 AM To: Arni Sumarlidason Cc: pos...@li...<mailto:pos...@li...> Subject: Re: [Postgres-xc-general] Heavy update utilization Inheritance is a problem here. Otherwise, we try to send DMLs involving a single table directly to the datanode, without any planning at coordinator. Unfortunately in this case since inheritance is involved, is row is modified first on coordinator and then changed at the datanode. If you are going to use inheritance a lot, may be you want to take up optimizations for inheritance cases (this is in the context of other thread, where you have asked for a todo list.) On Fri, Apr 5, 2013 at 10:18 AM, Arni Sumarlidason <Arn...@md...<mailto:Arn...@md...>> wrote: Schema same as before, we left our schema inherited because we don't want to reload our data when support is pushed out. Think inheritance is also causing this issue as well? Statement: Update table set col = "stuff" where Id = 447938 Also might be worth mentioning we are using psycopg2 python connector. Thank you for your advice. Sent from my iPhone On Apr 4, 2013, at 11:57 PM, "Ashutosh Bapat" <ash...@en...<mailto:ash...@en...>> wrote: Can you please post your update query here with all the relevant definitions like table schema etc.? On Fri, Apr 5, 2013 at 3:15 AM, Arni Sumarlidason <Arn...@md...<mailto:Arn...@md...>> wrote: General, We had a problem doing updates on our database today, it seems like updates are a pretty heavy operation for the coordinator. They tack our machines at 60-70% utilization[1] with 5 update cursors, and for reasons unknown a 6th connection causes a cascade failure across all coordinators. Do you know what would cause this? [1] http://www.sumarlidason.com/perm/130404/load8.PNG<https://console.mxlogic.com/redir/?zC763hOYqejhOrv7cIcECzAQsCM0l6Rtyv93qlxO-bv5n4mrInoM-KEfs5wo4zt-psLuZXTLsTsTJ2rsWQ9YgRrpwHUj-aQpkZ0xOVIs-eodEIKfEII9ILCTXCMnWhEwdbomHip6fQbxZyV7Uv7jPiWq80L-CiNEwrmgSvCy1KszV2CPBm1KvxYY1NJ4SOrpop73zhO-Ur3Fk-amvt> - Four machines at bottom of screen are coordinators, which correspond to the thick utilization in the graph. ------------------------------------------------------------------------------ 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<https://console.mxlogic.com/redir/?zC763hOYqejhOrv7cIcECzAQsCM0lFkJnBY05x_X64E4sZlo-FrUyIvFlKdLFw5Y3zt-psLuZXTLsTsTJ2rsWQ9YgRrpwHUj-aQpkZ0xOVIs-eodEIKfEII9ILCTXCMnWhEwdbomHip6fQbxZyV7Uv7jPiWq80L-CiNEwrmgSvCy1KszV2CPBm1KvxYY1NJcSOrpop73zhO-UrlC3O> _______________________________________________ Postgres-xc-general mailing list Pos...@li...<mailto:Pos...@li...> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general<https://console.mxlogic.com/redir/?2eosod7bNEVd79JYsOMOyqejhOr9PCJhbcfBiteFlKdLt00_MdM-l9QM-l9OwXn5GQChzZ2UvoKh-7NQYTvCnbTLuZXTdTdXgCTeJ2v4dmSoa-4_yJ6lfg8sKr7fzC3qbbzWbb2rbVJ-VI5-Aq83iS5GQChzZ2UvoKh-7NQYQKCy0b_FAIq86RAdDVEwrD8-gFIVlwrDUvf0srpdICSm6hMUQsLK6XlrO> -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Paul J. <pb...@cm...> - 2013-04-08 19:59:00
|
Thanks for everyone's explanation of PRIMARY. It is much clearer now. I believe, then, that we may have uncovered a bug in PRIMARY. We created a new cluster (8 nodes, 3 coordinators), but with only one PRIMARY datanode. The PRIMARY was declared the same on all 3 coordinators. A table that was declared DISTRIBUTE BY REPLICATION and loaded by \copy did not have any rows present on the PRIMARY! Further, other tables with FK's referring to this table had RI failures when they were loaded, even though there were complete copies of the table in all the other non-PRIMARY datanodes. When we remade the cluster without any PRIMARY, this table loaded into all datanodes and there were no RI failures. Is this a bug? Unfortunately I won't be able to experiment with this until we finish executing our test plan, perhaps a few days. PJ >________________________________ > From: Koichi Suzuki <koi...@gm...> >To: Andrei Martsinchyk <and...@gm...> >Cc: "pos...@li..." <pos...@li...> >Sent: Sunday, April 7, 2013 9:23 AM >Subject: Re: [Postgres-xc-general] Questions about PRIMARY and a problem > > >Primary node is useful to maintain replicated table in a consistent status in all the datanode. All the writes to a replicated table goes first to the primary node so all the conflicts are resolved here and prevents conflict writes in other datanodes. In this sense, this may prvent some deadlocks but it does not remove the chance of deadlocks in general sense. > >On the othe hand, preferred node (datanode again) saves inter-server communication to read replciated table. It does not work to maintain replicated table consistensy but helps to gain some performance. > >Regards; >--- >Koichi Suzuki > > > >---------- >Koichi Suzuki > > >2013/4/7 Andrei Martsinchyk <and...@gm...> > > >> >> >> >> >>2013/4/7 Jov <am...@am...> >> >>datanode use primary node to solve replication table write,it is good,but how coordinator solve the dead lock problem? the coordinator nodes replication all globle catalog tables across coords,they are some kind replication table. >>> >>> >>>eg. >>> >>>client 1 run alter table tb on coord node A,it will lock local catalog data on A,and wait other coord node B. >>>client 2 run alter table tb on coord node B,it will lock local catalog data on B,and wait other coord node A. >>> >>> >>> >>>so how XC handle this dead lock? >>> >>> >> >> >>XC does not handle this, it will be deadlocked. >>Fortunately, chance of concurrent DDL much less then chance of concurrent replicated update. >> >> >> >> >>> >>>2013/4/6 Andrei Martsinchyk <and...@gm...> >>> >>>PRIMARY was introduced to avoid distributed deadlocks when updating replicated tables. >>>>To better understand the problem, imagine two transactions A and B are updating the same tuple in replicated concurrently. >>>>Normally coordinator sends the same commands to all datanodes at the same time, and if on some node A updates the tuple first, B will be waiting for the end of transaction A. If on other node B wins the race, both transactions will be waiting for each other. It is hard to detect such deadlock, the information about locks is not sent across network. >>>>But it is possible to avoid. The idea is to set one datanode as a primary, and execute distributed update on primary node first, and go on with other nodes only if operation succeeds on primary. >>>>With this approach row lock on primary would stop concurrent transactions from taking row locks on other nodes that could prevent command completion. >>>>So, to have this stuff working properly you should >>>>1) set only one datanode as a primary; >>>>2) if you have multiple coordinators, the same datanode should be set as a primary on each of them. >>>>Obvious drawback of the approach is double execution time of replicated updates. >>>>Note: "update" means any write access. >>>>Hope this answers 1)-3) >>>>Regarding 4), the query >>>> >>>> >>>>select nodeoids from pg_class, pgxc_class where pg_class.oid = pcrelid and relname = '<your table name>'; >>>> >>>> >>>> >>>>returns the list of nodes, where the specified table is distributed on. I guess there are 7 of them. >>>> >>>> >>>> >>>> >>>> >>>>2013/4/5 Paul Jones <pb...@cm...> >>>> >>>> >>>>>We are experimenting with an 8-datanode, 3-coordinator cluster and we >>>>>have some questions about the use of PRIMARY and a problem. >>>>> >>>>>The manual explains what PRIMARY means but does not provide much detail >>>>>about when you would use it or not use it. >>>>> >>>>>1) Can PRIMARY apply to coordinators and if so, when would you >>>>> want it or not? >>>>> >>>>>2) When would you use PRIMARY for datanodes or not, and would you >>>>> ever want more than one datanode to be a primary? >>>>> >>>>>3) Does a pgxc_node datanode entry on its own server have to be >>>>> the FQDN server name or can it be 'localhost'? >>>>> >>>>>4) We have a table that is defined as DISTRIBUTE BY REPLICATION. >>>>> It only loads on the first 7 nodes. It will just not load on >>>>> node 8. There are a lot of FK references from other tables to it, >>>>> but it itself only has a simple CHAR(11) PK, one constraint, >>>>> and 3 indices. >>>>> >>>>> Has anyone seen anything like this before? >>>>> >>>>>Thanks, >>>>>Paul Jones >>>>> >>>>>------------------------------------------------------------------------------ >>>>>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 >>>> >>>> >>>> >>>>------------------------------------------------------------------------------ >>>>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 >>>> >>>> >>> >>> >>> >>>-- >>>Jov >>> >>>blog: http:amutu.com/blog >> >> >> >> >>-- >>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 >> >> > >------------------------------------------------------------------------------ >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: Florent T. <mai...@td...> - 2013-04-08 18:30:05
|
Actually we found the issue. A bad copy paste!!!! Amazing, Thanks On 08/04/2013 16:30, Florent THOMAS wrote: > Hy everyone, > > I followed this tutorial : > http://michael.otacoo.com/postgresql-2/start-a-postgres-xc-cluster-in-more-or-less-10-commands/ > Everything seems to work > Then I would like to distribute my datas and followed the page 47 of > the tuto there : > http://images4.wikia.nocookie.net/__cb20130121060137/postgresxc/images/d/d6/20120515_PGXC_Tutorial_global_1.pdf > > Unfortunately, the command failed : > /CREATE TABLE florent(pk int, val int)// > //test-# DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;// > //ERROR: syntax error at or near > "DISTRIBUTE BY REPLICATION TO NODE dn1"// > //LINE 2: DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;// > / > I've tried to find some answers on the net without success, > > Any help would be appreciated, > > regards, > > Florent THOMAS > > > ------------------------------------------------------------------------------ > 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: Abbas B. <abb...@en...> - 2013-04-08 15:10:46
|
On Mon, Apr 8, 2013 at 7:30 PM, Florent THOMAS <mai...@td...> wrote: > Hy everyone, > > I followed this tutorial : > http://michael.otacoo.com/postgresql-2/start-a-postgres-xc-cluster-in-more-or-less-10-commands/ > Everything seems to work > Then I would like to distribute my datas and followed the page 47 of the > tuto there : > http://images4.wikia.nocookie.net/__cb20130121060137/postgresxc/images/d/d6/20120515_PGXC_Tutorial_global_1.pdf > > Unfortunately, the command failed : > *CREATE TABLE florent(pk int, val int)** > **test-# DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;** > **ERROR: syntax error at or near "DISTRIBUTE BY REPLICATION TO NODE dn1"* > * > **LINE 2: DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;* > Please use parenthesis around the datanode list. E.g. CREATE TABLE florent(pk int, val int) DISTRIBUTE BY REPLICATION TO NODE (dn1, dn2); > * > * > I've tried to find some answers on the net without success, > > Any help would be appreciated, > > regards, > > Florent THOMAS > > > ------------------------------------------------------------------------------ > 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 > > -- -- 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: Florent T. <mai...@td...> - 2013-04-08 14:43:41
|
Hy everyone, I followed this tutorial : http://michael.otacoo.com/postgresql-2/start-a-postgres-xc-cluster-in-more-or-less-10-commands/ Everything seems to work Then I would like to distribute my datas and followed the page 47 of the tuto there : http://images4.wikia.nocookie.net/__cb20130121060137/postgresxc/images/d/d6/20120515_PGXC_Tutorial_global_1.pdf Unfortunately, the command failed : /CREATE TABLE florent(pk int, val int)// //test-# DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;// //ERROR: syntax error at or near "DISTRIBUTE BY REPLICATION TO NODE dn1"// //LINE 2: DISTRIBUTE BY REPLICATION TO NODE dn1, dn2;// / I've tried to find some answers on the net without success, Any help would be appreciated, regards, Florent THOMAS |
|
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 > > |
|
From: Theodotos A. <th...@ub...> - 2013-04-08 09:02:42
|
On 04/08/2013 06:52 AM, Nikhil Sontakke wrote: > Hi Theodotos, > >> Automatic monitoring and failover has not been provided yet. As Michael >> suggested, yes it's up to you at present. Sakata-san at NTT announced that >> they're developing XC RA for pacemaker/heartbeat (I hope it runs with >> Corosync too). >> > Yes, resource agents for pacemaker/corosync indeed work quite well for > XC HA. And yeah using heartbeat or corosync should be equivalent > mostly. > > We have indeed written custom agents for datanode and GTM monitoring > and HA using Corosync/Pacemaker and they work pretty well. > > Regards, > Nikhils This is great! Are these RA open/freely available? Download Links? Maybe some guide/documentation? |
|
From: Theodotos A. <th...@ub...> - 2013-04-08 08:58:58
|
This is something I didn't thought of. Instead of building your own scripts just use pgxc_ctl failover functionality. Thanks Koichi. On 04/07/2013 05:27 PM, Koichi Suzuki wrote: > Automatic monitoring and failover has not been provided yet. As > Michael suggested, yes it's up to you at present. Sakata-san at NTT > announced that they're developing XC RA for pacemaker/heartbeat (I > hope it runs with Corosync too). > > Failover steps will be found in pgx_ctl (bash version). I do hope > it helps people to build their own falover system. I'm about to commit > C-version of pgxc_ctl, which is much faster and more flexible than > bash version. > > Regards; > > ---------- > Koichi Suzuki > > > 2013/4/6 Michael Paquier <mic...@gm... > <mailto:mic...@gm...>> > > > > > On Sat, Apr 6, 2013 at 4:34 PM, Theodotos Andreou > <th...@ub... <mailto:th...@ub...>> wrote: > > Guys hi, > > I finally managed, with the help of pgxc_ctl to setup a HA > postgres-xc > cluster. I have 4 nodes (coord/datanode) and 2 GTMs > (active/)failover as > per the default setup of pgxc_ctl. > > Now I have some questions to get me started. > > 1) When using the standard CREATE TABLE sql commands the > tables are > distributed or replicated? I intend to copy the db schema from > my live > postgresql system and I want to know what the default behavior is > > You can specify the distribution type by using clause DISTRIBUTE > BY of CREATE TABLE. > Clause TO NODE/GROUP can be used to specified a list of nodes > where data is distributed. > Documentation is your friend: > http://postgres-xc.sourceforge.net/docs/1_0_2/sql-createtable.html > > > 2) Should there be an automatic failover mechanism when one of the > machines fail? What do you recommend? (heartbeat/pacemaker, > keepalined, > monit, ...) > > This is really up to you. Hearbeat would be fine, even Corosync/RDBMS. > Why not using the one you are the kost familiar with? > > 3) The default setup creates 4 coordinators: node1:20004, > node2:20005, > node3:20004, node4:20005. Is it better to use a TCP/IP load > balancer to > accept traffic at port 5432 and load balance to the 4 nodes or > use an > application load balancer instead (pgpool, pgbouncer, ...) > > I recall that an instance of pgbouncer can only pool connections > to 1 node. So pgpool? > > 4) How about optimizations? Shared memory and such? Should it > be split > by 4 since there are 4 instances on each server? > > Those are huge questions. First, you should setup a Datanode as > you would set up a normal PG server. > > For Coordinators, shared_buffers can be reduced to a quantity > enough to cache the catalog data as it doesn't have any relations. > Depending on your application, you might for example not need to > set up a high value of work_mem if you are able to push down sort > operations to Datanodes for example. > -- > Michael > > ------------------------------------------------------------------------------ > 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 > > |
|
From: Theodotos A. <th...@ub...> - 2013-04-08 08:52:26
|
On 04/07/2013 08:45 AM, Abbas Butt wrote: > > > On Sun, Apr 7, 2013 at 8:25 AM, Theodotos Andreou <th...@ub... > <mailto:th...@ub...>> wrote: > > On 04/06/2013 04:00 PM, Michael Paquier wrote: >> >> >> >> On Sat, Apr 6, 2013 at 4:34 PM, Theodotos Andreou >> <th...@ub... <mailto:th...@ub...>> wrote: >> >> Guys hi, >> >> I finally managed, with the help of pgxc_ctl to setup a HA >> postgres-xc >> cluster. I have 4 nodes (coord/datanode) and 2 GTMs >> (active/)failover as >> per the default setup of pgxc_ctl. >> >> Now I have some questions to get me started. >> >> 1) When using the standard CREATE TABLE sql commands the >> tables are >> distributed or replicated? I intend to copy the db schema >> from my live >> postgresql system and I want to know what the default behavior is >> >> You can specify the distribution type by using clause DISTRIBUTE >> BY of CREATE TABLE. >> Clause TO NODE/GROUP can be used to specified a list of nodes >> where data is distributed. >> Documentation is your friend: >> http://postgres-xc.sourceforge.net/docs/1_0_2/sql-createtable.html > If I use pg_dump then the resulting data that comes from > "traditional" postgresql will not have any "DISTRIBUTE BY" clause. > According to the manual: > > "If DISTRIBUTE BY is not specified, columns with UNIQUE constraint > will be chosen as the distribution key. If no such column is > specified, distribution column is the first eligible column in the > definition. If no such column is found, then the table will be > distributed by ROUND ROBIN. " > > So the default behavior for "traditional" CREATE TABLE statements > is ROUND ROBIN, right? > > > No, If the user does not specify any DISTRIBUTE BY clause, then the > system first tries to distribute the table by hash, and for that it > uses the first column that is hash distributable. Many common types > (int, float, text etc) can be taken as hash distributable. However if > the table does not contain any column that can be hash distributed > then the system falls back to ROUND ROBIN. > > > >> >> 2) Should there be an automatic failover mechanism when one >> of the >> machines fail? What do you recommend? (heartbeat/pacemaker, >> keepalined, >> monit, ...) >> >> This is really up to you. Hearbeat would be fine, even >> Corosync/RDBMS. >> Why not using the one you are the kost familiar with? > > I have experience with heartbeat and monit (not realy a HA > mechanism but with scripts you can do almost everything). But I > would feel more comfortable if I see a HOWTO of someone that > already implemented automatic failover in production. > > This presentation: > http://wiki.postgresql.org/images/7/7a/Postgres-xc-sharednothing-pgopen2012.pdf > says (page 34) that "Linux-HA Japan team is actively working for > the above" (HA resource agents for pacemaker). Is there any > progress on that? Some code even alpha/unstable? > > >> 3) The default setup creates 4 coordinators: node1:20004, >> node2:20005, >> node3:20004, node4:20005. Is it better to use a TCP/IP load >> balancer to >> accept traffic at port 5432 and load balance to the 4 nodes >> or use an >> application load balancer instead (pgpool, pgbouncer, ...) >> >> I recall that an instance of pgbouncer can only pool connections >> to 1 node. So pgpool? > > Do you see any advantages/disadvantages between a TCP/IP load > balancer (e.g. keepalived/IPVS) with an application level load > balancer like pgpool? Which one do you use? > > >> 4) How about optimizations? Shared memory and such? Should it >> be split >> by 4 since there are 4 instances on each server? >> >> Those are huge questions. First, you should setup a Datanode as >> you would set up a normal PG server. >> >> For Coordinators, shared_buffers can be reduced to a quantity >> enough to cache the catalog data as it doesn't have any >> relations. Depending on your application, you might for example >> not need to set up a high value of work_mem if you are able to >> push down sort operations to Datanodes for example. > > Makes sense to give more shared buffers for datanodes. My > application already uses "traditional" postgresql and we would > like not to have to do code changes on it. How can you "push down > sort operations to Datanodes"? Change the code on the application > or within postgres-xc? > > > Within postgres-xc, when the coordinator receives the query it passes > it through postgres-xc planner which decides whether the query can be > directly shipped to datanodes or not. If not the query then passes > through standard postgres planner. > > >> -- >> Michael > > Thanks for your reply Michael! Please excuse me if some of the > questions appear silly. I am a humble sysadmin and even though I > have setup databases like mysql and postgres, I have little > experience on the "internals" of databases. Postgres-xc is an even > more complicated system than traditional Linux RDBMS and I want to > clear my confusion a bit. > > ------------------------------------------------------------------------------ > 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 > > > > > -- > -- > Abbas > Architect > EnterpriseDB Corporation > The Enterprise PostgreSQL Company > > Phone: 92-334-5100153 > > Website: www.enterprisedb.com <http://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. Thanks Abbas. Very enlightening information. |
|
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: Koichi S. <koi...@gm...> - 2013-04-08 08:27:14
|
Hi, The steps you sent in the last mail seem to work fine. I wonder what happens after you checked everything is working. Do you want to initialize them again? init command starts all the components so you are ready to invoke psql sessions, createdb command, etc. Regards; ---------- Koichi Suzuki 2013/4/5 Theodotos Andreou <th...@ub...> > It turned out to be a severe stupidity condition :) > > I had the wrong subnet in the following config parameter: > > datanodePgHbaEntries=(192.168.20.0/24) > > As an apology please accept this mini howto for newbies like me :) > > > Postgres-xc with pgxc_ctl mini HOWTO: > ---------------------------------------------------- > > Assumptions: > > We have 1 control machine: > > node-pgxc-ctl > > 4 coord/datanode machines: > > node-pgxcdb01 - 04 > > 2 gtm machines: > > node-pgxcgtm01 - 02 > > We use the user postgres-xc and its home is /var/lib/postgres-xc. > > The path for postgres-xc is /var/lib/postgres-xc/pgxc and so is --prefix > > We have passwordless auth between all machines > > Our subnet is 192.168.20.0/24 > > Step 1: Build postgres-xc from source: > > > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure > --prefix=/var/lib/postgres-xc/pgxc > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install > > Step 2: Build postgres-xc contrib files: > > > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install > > Step 3: Build pgxc_monitor: > > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ > postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make install > > Step 4: Download pgxc_ctl > > postgres-xc@node-pgxc-ctl:~$ ls /var/lib/postgres-xc/bin ; echo $PATH > pgxc_ctl > > /var/lib/postgres-xc/bin:/var/lib/postgres-xc/pgxc/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games > > The ~/pgxc folder now exists only on the control machine. > > Step 5: Prepare config: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config ; ls pgxc/pgxcConf > pgxc/pgxcConf > > This is our config: > > http://pastebin.com/aqWBA5e9 > > Step 6: Deploy all: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl -v deploy all 2>&1 | tee deploy.log > > Now the ~/pgxc directory is deployed on all nodes > > Step 6: Init: > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl -v init 2>&1 | tee init.log > > Step 7: Monitor all: > > > postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all > GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm > GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: > /var/lib/postgres-xc/pgxc/nodes/gtm_pxy > Coordinator master (coord1): running. host: node-pgxcdb01, port: 20004, > dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord2): running. host: node-pgxcdb02, port: 20005, > dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord3): running. host: node-pgxcdb03, port: 20004, > dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator master (coord4): running. host: node-pgxcdb04, port: 20005, > dir: /var/lib/postgres-xc/pgxc/nodes/coord > Coordinator slave (coord1): running. host: node-pgxcdb02, port: 20004, > dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord2): running. host: node-pgxcdb03, port: 20005, > dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord3): running. host: node-pgxcdb04, port: 20004, > dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Coordinator slave (coord4): running. host: node-pgxcdb01, port: 20005, > dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave > Datanode master (datanode1): running. host: node-pgxcdb01, port: 20008, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode2): running. host: node-pgxcdb02, port: 20009, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode3): running. host: node-pgxcdb03, port: 20008, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode master (datanode4): running. host: node-pgxcdb04, port: 20009, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_master > Datanode slave (datanode1): running. host: node-pgxcdb02, port: 20008, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode2): running. host: node-pgxcdb03, port: 20009, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode3): running. host: node-pgxcdb04, port: 20008, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > Datanode slave (datanode4): running. host: node-pgxcdb01, port: 20009, > dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave > > Now the real fun begins! > > > > On 04/04/2013 09:40 AM, Koichi Suzuki wrote: > > Are there other usual postgresql files on these directories, for example, > postgresql.conf? Initdb utility creates them, which pgxc_ctl invokes with > init command. It seems that initdb did not work correctly. > > If you can do the things again, could you run pgxc_ctl init with -v > option, such as pgxc_ctl -v init? -v will give you detailed feedback. > Also, if possible, could you send me your configuration file? I will > look into it. > > Best Regards; > > ---------- > Koichi Suzuki > > > 2013/4/3 Theodotos Andreou <th...@ub...> > >> Hi Koichi, >> >> See answers below >> >> >> On 04/01/2013 07:32 AM, Koichi Suzuki wrote: >> >> Please check if --prefix (or /usr/local/pgsql, the default) is the same >> as your pgxc_ctl configuration's xc installation directory. This is needed >> to make "deploy all" work correctly. >> >> >> They are the same: >> ./configure --prefix=/var/lib/postgres-xc/pgxc >> pgxcInstallDir=/var/lib/postgres-xc/pgxc >> >> >> deploy all works without errors >> >> >> >> >> pgxc_monitor uses psql ... -c "select 1" to check if the target is >> running. That is, it checks if the target can handle a statement >> correctly. Sometimes, for example, if the slave is connected >> synchronously (pgxc_ctl uses synchronous replication) and the slave does >> not work, the master cannot handle incoming statements until the slave >> replies to the master correctly. This is one possibility that the master >> is determined "not working". (In 1.1, I'm improving this). >> >> >> postgres-xc@node-pgxcdb01:~$ psql pgxc_ctl init gives: >> >> http://pastebin.com/sccGQm1u >> >> Apparently the problem is here: >> bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or >> directory >> bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or >> directory >> bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or >> directory >> bash: /var/lib/postgres-xc/pgxc/nodes/coord/pg_hba.conf: No such file or >> directory >> >> Any idea why it fails to create them? >> >> >> Is this the correct test command? : >> >> postgres-xc@node-pgxcdb01:~$ psql -p 20008 postgres -c select 1 >> psql: FATAL: role "1" does not exist >> >> >> >> >> Could you please check one of the log for datanode master/slave and see >> if there's any log indicating errors? This is very helpful to determine >> what is wrong. >> >> Logs on dn_master: >> >> postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat >> postgresql-2013-04-03_155857.log >> LOG: database system was shut down at 2013-04-03 15:57:49 EEST >> LOG: database system is ready to accept connections >> LOG: autovacuum launcher started >> FATAL: no pg_hba.conf entry for replication connection from host >> "192.168.20.103", user "postgres-xc" >> LOG: received smart shutdown request >> LOG: autovacuum launcher shutting down >> LOG: shutting down >> LOG: database system is shut down >> >> postgres-xc@node-pgxcdb01:~/pgxc/nodes/dn_master/pg_log$ cat >> postgresql-2013-04-03_160100.log >> LOG: database system was shut down at 2013-04-03 15:59:04 EEST >> LOG: database system is ready to accept connections >> LOG: autovacuum launcher started >> FATAL: no pg_hba.conf entry for host "192.168.20.101", user >> "postgres-xc", database "postgres" >> FATAL: no pg_hba.conf entry for host "192.168.20.101", user >> "postgres-xc", database "postgres" >> FATAL: role "1" does not exist >> FATAL: database "1" does not exist >> FATAL: role "1" does not exist >> >> dn_slave failed to replicate so, no logs. >> >> >> I think these partly answer your question a) and c). >> >> I don't think b) works here, because deploy all just copies all the >> binaries to the target servers. From your report, if ./configure and >> pgxc_ctl configuration matches, I found no problem in it. >> >> Hope it helps. >> >> Please feel free to write for further help. >> >> Regards; >> --- >> Koichi Suzuki >> >> ---------- >> Koichi Suzuki >> >> >> 2013/3/30 Theodotos Andreou <th...@ub...> >> >>> Guys I am using pgxc_ctl to built a HA postgres-xc cluster with 4 >>> coordinator/datanodes and 2 gtm nodes: >>> >>> I use the postgres-xc user and I have passwordless ssh between all nodes >>> and the separate pgxc_ctl machine. >>> The dirs ~/bin and ~/pgxc/bin are in the $PATH of postgres-xc user. >>> >>> These are the steps I followed: >>> >>> 1) Complile pgxc and tools: >>> >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ ./configure >>> --prefix=/var/lib/postgres-xc/pgxc >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ make install >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2$ cd contrib/ >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ make install >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib$ cd pgxc_monitor/ # This >>> is not included in latest pgxc. I had to download it separately. >>> postgres-xc@node-pgxc-ctl:~/pgxc-v1.0.2/contrib/pgxc_monitor$ make >>> install >>> >>> 2) Download script: >>> >>> I downloaded the pgxc_ctl in ~/bin and patched line 4566 (put a space in >>> front of ']') >>> >>> 3) Cinfiguration of pgxc_ctl >>> >>> Created the config file: >>> >>> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl prepare config >>> >>> I edited ~/pgxc/pgxcConf such as: >>> >>> http://pastebin.com/DHwpwdr1 >>> >>> 4) Deployed: >>> >>> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl deploy all >>> wk.tgz 100% 7365KB 7.2MB/s 00:00 >>> wk.tgz 100% 7365KB 7.2MB/s 00:00 >>> wk.tgz 100% 7365KB 7.2MB/s 00:00 >>> wk.tgz 100% 7365KB 7.2MB/s 00:00 >>> wk.tgz 100% 7365KB 7.2MB/s 00:00 >>> wk.tgz 100% 7365KB 7.2MB/s 00:01 >>> >>> deploy log: >>> >>> http://pastebin.com/eETjNmmV >>> >>> 5) Initialize all: >>> >>> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl init >>> >>> This gives a lot of errors. Init log: >>> >>> http://pastebin.com/ML5HLJ2i >>> >>> 6) Monitor all >>> >>> postgres-xc@node-pgxc-ctl:~$ pgxc_ctl monitor all >>> GTM master (gtm): running. host: node-pgxcgtm01, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm >>> GTM slave (gtm): running. host: node-pgxcgtm02, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm >>> GTM proxy (gtm_pxy1): running. host: node-pgxcdb01, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >>> GTM proxy (gtm_pxy2): running. host: node-pgxcdb02, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >>> GTM proxy (gtm_pxy3): running. host: node-pgxcdb03, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >>> GTM proxy (gtm_pxy4): running. host: node-pgxcdb04, port: 20001, dir: >>> /var/lib/postgres-xc/pgxc/nodes/gtm_pxy >>> Coordinator master (coord1): running. host: node-pgxcdb01, port: >>> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >>> Coordinator master (coord2): running. host: node-pgxcdb02, port: >>> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >>> Coordinator master (coord3): running. host: node-pgxcdb03, port: >>> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord >>> Coordinator master (coord4): running. host: node-pgxcdb04, port: >>> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord >>> Coordinator slave (coord1): running. host: node-pgxcdb02, port: >>> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >>> Coordinator slave (coord2): running. host: node-pgxcdb03, port: >>> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >>> Coordinator slave (coord3): running. host: node-pgxcdb04, port: >>> 20004, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >>> Coordinator slave (coord4): running. host: node-pgxcdb01, port: >>> 20005, dir: /var/lib/postgres-xc/pgxc/nodes/coord_slave >>> Datanode master (datanode1): not running. host: node-pgxcdb01, port: >>> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >>> Datanode master (datanode2): not running. host: node-pgxcdb02, port: >>> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >>> Datanode master (datanode3): not running. host: node-pgxcdb03, port: >>> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >>> Datanode master (datanode4): not running. host: node-pgxcdb04, port: >>> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_master >>> Datanode slave (datanode1): not running. host: node-pgxcdb02, port: >>> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >>> Datanode slave (datanode2): not running. host: node-pgxcdb03, port: >>> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >>> Datanode slave (datanode3): not running. host: node-pgxcdb04, port: >>> 20008, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >>> Datanode slave (datanode4): not running. host: node-pgxcdb01, port: >>> 20009, dir: /var/lib/postgres-xc/pgxc/nodes/dn_slave >>> >>> But not all of the above information is true. Coordinators are all up >>> but only the datanode masters are working: >>> >>> # dsh -a 'echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | >>> grep postgres | grep dn' >>> >>> node-pgxcdb01 >>> ------------ >>> 999 13843 0.0 0.3 53236 7308 ? S 13:15 0:00 >>> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >>> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >>> root 18229 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> node-pgxcdb02 >>> ------------ >>> 999 12911 0.0 0.3 53232 7304 ? S 13:15 0:00 >>> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >>> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >>> root 17295 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> node-pgxcdb03 >>> ------------ >>> 999 12918 0.0 0.3 53232 7312 ? S 13:15 0:00 >>> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >>> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >>> root 17383 0.0 0.0 11008 1436 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> node-pgxcdb04 >>> ------------ >>> 999 12920 0.0 0.3 53240 7316 ? S 13:15 0:00 >>> /var/lib/postgres-xc/pgxc/bin/postgres -X -D >>> /var/lib/postgres-xc/pgxc/nodes/dn_master -i >>> root 17270 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> node-pgxcgtm01 >>> ------------ >>> root 7087 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> node-pgxcgtm02 >>> ------------ >>> root 5913 0.0 0.0 11008 1432 ? Ss 14:21 0:00 bash -c >>> echo "" ; echo $HOSTNAME ; echo "------------" ; ps auxw | grep postgres >>> | grep dn >>> >>> >>> Trying to start the slaves manually I get: >>> postgres-xc@node-pgxcdb01:~$ /var/lib/postgres-xc/pgxc/bin/postgres -X >>> -D /var/lib/postgres-xc/pgxc/nodes/dn_slave/ -i >>> FATAL: "/var/lib/postgres-xc/pgxc/nodes/dn_slave" is not a valid data >>> directory >>> DETAIL: File "/var/lib/postgres-xc/pgxc/nodes/dn_slave/PG_VERSION" is >>> missing. >>> >>> The datanode slaves have not been initialized because pg_basebackup >>> fails with: >>> >>> Questions: >>> >>> a) Any idea what I am doing wrong? Init logs are not very clear what is >>> the problem. >>> >>> b) Can I run "pgxc_ctl deploy all" again? Will this mess up the current >>> setup if I do? >>> >>> c) Why does pgxc_monitor reports that datanode masters are down when are >>> in fact working? >>> >>> >>> ------------------------------------------------------------------------------ >>> Own the Future-Intel(R) 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://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 >>> _______________________________________________ >>> 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: Nikhil S. <ni...@st...> - 2013-04-08 03:53:04
|
Hi Theodotos, > Automatic monitoring and failover has not been provided yet. As Michael > suggested, yes it's up to you at present. Sakata-san at NTT announced that > they're developing XC RA for pacemaker/heartbeat (I hope it runs with > Corosync too). > Yes, resource agents for pacemaker/corosync indeed work quite well for XC HA. And yeah using heartbeat or corosync should be equivalent mostly. We have indeed written custom agents for datanode and GTM monitoring and HA using Corosync/Pacemaker and they work pretty well. Regards, Nikhils -- StormDB - http://www.stormdb.com The Database Cloud |
|
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 > |
43 messages has been excluded from this view by a project administrator.
