|
From: Sergio S. <ser...@da...> - 2014-02-25 22:12:29
|
Hi. I tried postgres xc 1.1 with these patches and postgis patch. Every worked perfect. These patches are compatible. However I only was able to install 1.5 and 2.0 versions of postgis. I had the following error with postgis 2.1.1 version: ERROR: unsafe use of pseudo-type "internal" DETAIL: Transition type can not be "internal". But I think that this trouble is for another thread. I will use postgres xc 1.1 with postgis 2.0 in a production enviroment. I will let you know my results. Thanks for help. 2014-02-23 21:05 GMT-05:00 Masataka Saito <pg...@gm...>: > On 22 February 2014 01:38, Sergio Sinuco > <ser...@da...> wrote: > > I forgot to say that when the cluster start after crash, sequences of > tables > > advance two thousand units. For example, before kill gtm process, > sequence > > was in 4. After restart, sequence's value of first insertion was in > 2005. > > It's a feature. > GTM doesn't write sequence values into the disk at each assignment for > performance. GTM ensures the sequence value will unique but doesn't > ensure it will continuous. It could skip 2000 at maximum. > > > > > > > 2014-02-21 11:32 GMT-05:00 Sergio Sinuco < > ser...@da...>: > > > >> Hi. Thanks for reply. Effectively I applied the patches to 1.1 version > and > >> It worked. However I had to remove register.node files in GTM and GTM > Proxy > >> too because if I didn't do it then the cluster didn't work. > >> > >> Now I will try 1.1 version with these patches and postgis patch in order > >> to find if they are compatible. I will let you know my results. > >> > >> I will try 1.2 version too. > > The patch Mr.Suzuki suggested is not for the issue I told. > > Regards. > > >> > >> Thanks. > >> > >> > >> 2014-02-19 21:15 GMT-05:00 Masataka Saito <pg...@gm...>: > >> > >>> I'm afraid you got this issue. Can you check logs in GTM and GTM proxy? > >>> https://sourceforge.net/p/postgres-xc/bugs/474/ > >>> > >>> If it prove right, please take the following steps. > >>> 1. Stop all component > >>> 2. Remove register.node in GTM and GTM Proxy > >>> 3. Start GTM > >>> 4. Start GTM proxy > >>> 5. Start coordinators and datanodes > >>> > >>> Following materials will be help you to configure. > >>> * Postgres Open 2013 (Especially SPOF Analysis in Slide deck) > >>> > >>> > http://sourceforge.net/apps/mediawiki/postgres-xc/index.php?title=Presentation_Materials > >>> > >>> And the configuration topics described in these materials are > >>> deprecated yet, but very helpful to know what pgxc_ctl does. > >>> * PGDay.EU, Oct 24th, 2012, Prague, Czeck > >>> > >>> > http://postgres-xc.sourceforge.net/misc-docs/Prague_Presentation_20121024.pdf > >>> * Presentation at PGConfChina 2012, Jun16th, 2012, Beijing, China (I > >>> believe this is the best material for geeks) > >>> > >>> > http://postgres-xc.sourceforge.net/misc-docs/PGConfChina_20120610_Distribution.pdf > >>> > >>> Regards. > >>> > >>> On 20 February 2014 02:03, Sergio Sinuco > >>> <ser...@da...> wrote: > >>> > Hello everybody. > >>> > > >>> > I just begin to try postgrexc 1.1. I have followed configuration > >>> > tutorial > >>> > for real servers in postgresxc.wikia.com > >>> > > >>> > http://postgresxc.wikia.com/wiki/Real_Server_configuration > >>> > > >>> > I setup three nodes. The first one with a GTM. The second and third > >>> > with a > >>> > GTM Proxy, a datanode and a coordinator in each one. > >>> > > >>> > Everything is OK, until I kill the GTM process in first node. After > >>> > restart > >>> > everything in all nodes I can't insert new data in tables. When I try > >>> > it, > >>> > following message is showed: > >>> > > >>> > ERROR: > >>> > STATEMENT: INSERT INTO public.test(name) VALUES ('CARLOS'::text) > >>> > > >>> > Then, I can't connect to coordinators and following message is > showed: > >>> > > >>> > ERROR: GTM error, could not obtain snapshot XID = 0 > >>> > WARNING: can not connect to GTM: Connection refused > >>> > > >>> > I know that there is a way to configure Postgres-XC in order to have > >>> > high > >>> > availability (GTM Stand By and other stuff), but the question is, > when > >>> > GTM > >>> > process and even its contingency crash there is no way to get a right > >>> > behaviour of the cluster? > >>> > > >>> > Thanks. > >>> > > >>> > -- > >>> > Sergio E. Sinuco Leon > >>> > Arquitecto de soluciones > >>> > Datatraffic S.A.S. > >>> > Móvil: (57) 310 884 26 50 > >>> > Fijo (+571) 7426160 Ext 115 > >>> > Calle 93 # 15-27 Ofc. 502 > >>> > Calle 29 # 6 - 94 Ofc. 601 > >>> > Bogotá, Colombia. > >>> > www.datatraffic.com.co > >>> > > >>> > > >>> > > ------------------------------------------------------------------------------ > >>> > Managing the Performance of Cloud-Based Applications > >>> > Take advantage of what the Cloud has to offer - Avoid Common > Pitfalls. > >>> > Read the Whitepaper. > >>> > > >>> > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > >>> > _______________________________________________ > >>> > Postgres-xc-general mailing list > >>> > Pos...@li... > >>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > >>> > > >> > >> > >> > >> > >> -- > >> Sergio E. Sinuco Leon > >> Arquitecto de soluciones > >> Datatraffic S.A.S. > >> Móvil: (57) 310 884 26 50 > >> Fijo (+571) 7426160 Ext 115 > >> Calle 93 # 15-27 Ofc. 502 > >> Calle 29 # 6 - 94 Ofc. 601 > >> Bogotá, Colombia. > >> www.datatraffic.com.co > > > > > > > > > > -- > > Sergio E. Sinuco Leon > > Arquitecto de soluciones > > Datatraffic S.A.S. > > Móvil: (57) 310 884 26 50 > > Fijo (+571) 7426160 Ext 115 > > Calle 93 # 15-27 Ofc. 502 > > Calle 29 # 6 - 94 Ofc. 601 > > Bogotá, Colombia. > > www.datatraffic.com.co > -- Sergio E. Sinuco Leon Arquitecto de soluciones Datatraffic S.A.S. Móvil: (57) 310 884 26 50 Fijo (+571) 7426160 Ext 115 Calle 93 # 15-27 Ofc. 502 Calle 29 # 6 - 94 Ofc. 601 Bogotá, Colombia. www.datatraffic.com.co |