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
(1) |
2
(4) |
3
|
4
|
5
|
6
|
7
(4) |
8
(2) |
9
|
10
|
11
|
12
|
13
|
14
(4) |
15
(4) |
16
|
17
|
18
|
19
|
20
|
21
(6) |
22
(1) |
23
|
24
|
25
|
26
(3) |
27
(6) |
28
|
29
(1) |
30
|
|
From: Koichi S. <koi...@gm...> - 2012-11-26 12:03:13
|
Anyway, HA configuration parameters for GTM proxy in the current master is not backward-compatible. They are drastically simplified and the setting of the patch will be gone. This is quite simple to configure. So this is not the back port but is an improvement to decrease an impact to remove gtm_connect_retry_count. I understand this is not with minor release policy but I think this helps for people trying HA capability with 1.0.x releases. Regards; ---------- Koichi Suzuki 2012/11/26 Pavan Deolasee <pav...@gm...>: > > > > On Mon, Nov 26, 2012 at 2:59 PM, Koichi Suzuki > <koi...@us...> wrote: >> >> Project "Postgres-XC". >> >> The branch, REL1_0_STABLE has been updated >> > > > > Should we really be back-patching such changes ? Does this also involve some > bug fixes ? > > Thanks, > Pavan > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > Postgres-xc-committers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers > |
From: Pavan D. <pav...@gm...> - 2012-11-26 10:00:53
|
On Mon, Nov 26, 2012 at 2:59 PM, Koichi Suzuki < koi...@us...> wrote: > Project "Postgres-XC". > > The branch, REL1_0_STABLE has been updated > Should we really be back-patching such changes ? Does this also involve some bug fixes ? Thanks, Pavan |
From: Koichi S. <koi...@us...> - 2012-11-26 09:29:25
|
Project "Postgres-XC". The branch, REL1_0_STABLE has been updated via 8b1571514642ab42f8b26eb384bfef89a94d8afd (commit) from c0b19be8fa168813688a914e07b3f5638b3db069 (commit) - Log ----------------------------------------------------------------- http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8b1571514642ab42f8b26eb384bfef89a94d8afd commit 2912d566a2a8dc5f0ef0fe8f4c1b85addc59c3f5 Author: Abbas <abb...@en...> Date: Wed Nov 21 21:31:09 2012 +0500 This patch moves invocation of XC specific DML planning at the right place. The wrong location was uncovered while providing support for RETURNING. The previous code was unable to handle DMLs in WITH queries. Since WITH queries were blocked due to unsupported feature, hence the problem remained hidden previously. M src/backend/optimizer/plan/pgxcplan.c M src/backend/optimizer/plan/planner.c M src/include/optimizer/pgxcplan.h ----------------------------------------------------------------------- Summary of changes: doc-xc/src/sgml/config.sgmlin | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Postgres-XC |