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
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
(1) |
5
(1) |
6
(1) |
7
|
8
(1) |
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
From: Abbas B. <abb...@te...> - 2011-03-05 06:36:53
|
On Fri, Mar 4, 2011 at 8:06 PM, Lionel Frachon <lio...@gm...>wrote: > Hello, > > I'm starting an evaluation of the cluster (not having any PG > background, but Oracle & MySql for years...), and some questions > appear to me after reading the doc, any help appreciated. > Thank you, I would suggest playing around with plain PG first. That would help you a lot. > > My actual setup is : > pgxc1 for GTM, Coordinator and datanode > pgxc2 for datanode only > You mean you will have 2 computers, one will run GTM, Coordinator and 1st datanode and the other the 2nd data node. If yes then this would be fine. BTW what Linux distribution will you be using? Please remember that for the first time gtm has to be started with -x option and it is better to start gtm before you initdb for the coordinator and the 2 data nodes. For successive runs you should skip -x option. As a general rule you should always start gtm first then the data nodes and then the coordinator. > 1.General : Is a coordinator needed for each node, or one coordinator > 'to rule them all' can be setup ? > Yes, one coordinator serve multiple data nodes. > > 2. Configuration : What should be the differences between > postgresql.conf in /datanode and /coordinator, if there are any ? Yes each node in the cluster has to have a unique node ID, that is picked from the postgresql.conf. The coordinator needs to know the number of data nodes, and info required to to connect to them e.g. user name password etc Other than that I don't remember any thing on top of my head. Please take a look at the portions in the conf file specific to the XC, that would help. > Some > portions are they ignored for a specific function (ex : coordinator vs > datanode config, etc...) > In this can pg_hba.conf & postgresql.conf be shared for the same > server (maybe using symbolic links...) > No, as I explained earlier. > > 3. GTM : I get on second node an "WARNING: Do not have a GTM snapshot > available", can this be related to previous config files/setup ? > For the first data node the default configuration of a localhost GTM would be fine but for the 2nd data node you need to tell the data node where GTM is located, for this you need to change the gtm_host parameter in the postgresql.conf file of the 2nd datanode to the IP addeess of your first computer (which runs GTM). > > 4. Administration : are there ways of getting the online status of the > nodes from one node to another > This is currently under development. I can provide you details later. > > Thanks > > Lionel F. > > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |