Menu
▾
▴
postgres-xc-committers — Announces PG-XC repository commits
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(28) |
Jun
(12) |
Jul
(11) |
Aug
(12) |
Sep
(5) |
Oct
(19) |
Nov
(14) |
Dec
(12) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(18) |
Feb
(30) |
Mar
(115) |
Apr
(89) |
May
(50) |
Jun
(44) |
Jul
(22) |
Aug
(13) |
Sep
(11) |
Oct
(30) |
Nov
(28) |
Dec
(39) |
| 2012 |
Jan
(38) |
Feb
(18) |
Mar
(43) |
Apr
(91) |
May
(108) |
Jun
(46) |
Jul
(37) |
Aug
(44) |
Sep
(33) |
Oct
(29) |
Nov
(36) |
Dec
(15) |
| 2013 |
Jan
(35) |
Feb
(611) |
Mar
(5) |
Apr
(55) |
May
(30) |
Jun
(28) |
Jul
(458) |
Aug
(34) |
Sep
(9) |
Oct
(39) |
Nov
(22) |
Dec
(32) |
| 2014 |
Jan
(16) |
Feb
(16) |
Mar
(42) |
Apr
(179) |
May
(7) |
Jun
(6) |
Jul
(9) |
Aug
|
Sep
(4) |
Oct
|
Nov
(3) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
|
2
(2) |
|
3
(1) |
4
|
5
(2) |
6
|
7
(9) |
8
(4) |
9
|
|
10
|
11
|
12
(4) |
13
(1) |
14
(1) |
15
(4) |
16
|
|
17
|
18
(2) |
19
(2) |
20
|
21
(5) |
22
|
23
|
|
24
|
25
|
26
(2) |
27
|
28
(4) |
29
(3) |
30
|
|
From: Michael P. <mic...@us...> - 2012-06-02 20:38:51
|
Project "Postgres-XC".
The branch, master has been updated
via dfee5379109a757e1bfaa9fe59830e6fb05f6688 (commit)
from af488de7241de630c68c2f8a7a5ec6efb68ad083 (commit)
- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=dfee5379109a757e1bfaa9fe59830e6fb05f6688
commit dfee5379109a757e1bfaa9fe59830e6fb05f6688
Author: Michael Paquier <mi...@ot...>
Date: Sun Jun 3 05:29:06 2012 +0900
Block node registration for slave nodes and perform register at a stable state
Performing node registration on GTM just after postmaster start is dangerous
because the master/slave status of the node is unknown. So node
registration is done once node has reached a stable state, meaning that
Xlog process has confirmed to postmaster that recovery has been completed.
Registration is also blocked for slave nodes. A standby node is created
from a hot backup of its master so master and its slaves will share the
same node name. Two nodes are not authorized to register to GTM with the
same node name to avoid identification confusion in the cluster, so it
looks normal to let the master and the master only identify itself.
A a direct consequence, unregistration too is done only for master node.
Synchronous and asynchronous node replication works correctly with this fix,
as well as node promotion (Ex: "pg_ctl promote -D $DATA").
M src/backend/postmaster/postmaster.c
-----------------------------------------------------------------------
Summary of changes:
src/backend/postmaster/postmaster.c | 77 +++++++++++++++++++++++------------
1 files changed, 51 insertions(+), 26 deletions(-)
hooks/post-receive
--
Postgres-XC
|
|
From: Michael P. <mic...@us...> - 2012-06-02 20:38:47
|
Project "Postgres-XC".
The branch, REL1_0_STABLE has been updated
via 64c7d4d0aa32515db89069827e75a4997122b4bf (commit)
from 93aae0131c08cc5204562e7ce335f2446fc431af (commit)
- Log -----------------------------------------------------------------
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=64c7d4d0aa32515db89069827e75a4997122b4bf
commit dfee5379109a757e1bfaa9fe59830e6fb05f6688
Author: Michael Paquier <mi...@ot...>
Date: Sun Jun 3 05:29:06 2012 +0900
Block node registration for slave nodes and perform register at a stable state
Performing node registration on GTM just after postmaster start is dangerous
because the master/slave status of the node is unknown. So node
registration is done once node has reached a stable state, meaning that
Xlog process has confirmed to postmaster that recovery has been completed.
Registration is also blocked for slave nodes. A standby node is created
from a hot backup of its master so master and its slaves will share the
same node name. Two nodes are not authorized to register to GTM with the
same node name to avoid identification confusion in the cluster, so it
looks normal to let the master and the master only identify itself.
A a direct consequence, unregistration too is done only for master node.
Synchronous and asynchronous node replication works correctly with this fix,
as well as node promotion (Ex: "pg_ctl promote -D $DATA").
M src/backend/postmaster/postmaster.c
-----------------------------------------------------------------------
Summary of changes:
src/backend/postmaster/postmaster.c | 77 +++++++++++++++++++++++------------
1 files changed, 51 insertions(+), 26 deletions(-)
hooks/post-receive
--
Postgres-XC
|
