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
|
3
|
4
|
5
|
6
(4) |
7
(1) |
8
(6) |
9
(3) |
10
|
11
|
12
|
13
(1) |
14
(4) |
15
(1) |
16
(1) |
17
|
18
|
19
|
20
|
21
|
22
(8) |
23
|
24
|
25
|
26
(2) |
27
(3) |
28
(1) |
29
(6) |
30
(1) |
31
|
From: Pavan D. <pav...@gm...> - 2012-03-06 15:20:32
|
Hi All, This commit message looks a bit weird. I merged from another branch which had 6-7 commits. The commit IDs are reflected correctly in the message, but the last commit message is replicated. Not sure what to blame. The git log shows different log message for every commit though. Let me know if you see any issue with the repository. Thanks, Pavan On Tue, Mar 6, 2012 at 6:43 PM, Pavan Deolasee < pa...@us...> wrote: > Project "Postgres-XC". > > The branch, master has been updated > via 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb (commit) > via f5c981669460bcd696a266c9a336798b29769148 (commit) > via 8efdf2b44e1cd42f255330abb1388a11fa0cec49 (commit) > via 30dc60778733551b30c74344532152be6bab675f (commit) > via 9f63e43eae0e69554fafd5b9032c662cf9ae120b (commit) > via 8b7444f3c88104d0f078fd49514bc692d95ffed0 (commit) > via c547574f4ba05ae21958b5a32b4742c84ce448c9 (commit) > via 57e659829550d3e4c4dd82c7fef5cd3f20e94a48 (commit) > via 9bf0a59a76844e4e673c871790e9e49375b27eb2 (commit) > via 738e13b7a7945da99f06ad913a4fe570f3337abc (commit) > from e1d299020b4f8cb04d11bb5f51bd86871e3e8881 (commit) > > > - Log ----------------------------------------------------------------- > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=f5c981669460bcd696a266c9a336798b29769148 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8efdf2b44e1cd42f255330abb1388a11fa0cec49 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=30dc60778733551b30c74344532152be6bab675f > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9f63e43eae0e69554fafd5b9032c662cf9ae120b > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8b7444f3c88104d0f078fd49514bc692d95ffed0 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=c547574f4ba05ae21958b5a32b4742c84ce448c9 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=57e659829550d3e4c4dd82c7fef5cd3f20e94a48 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9bf0a59a76844e4e673c871790e9e49375b27eb2 > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > > http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=738e13b7a7945da99f06ad913a4fe570f3337abc > > commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb > Author: Pavan Deolasee <pav...@gm...> > Date: Tue Mar 6 18:38:30 2012 +0530 > > Remove an assertion that checks for calling AbortTransaction on an > already > aborted transaction. We have seen this happening when a ROLLBACK > statement > is canceled by the client. We believe this is a PostgreSQL issue, but > gets > manifested by XC. We should discuss this further on the hackers list > > M src/backend/storage/ipc/procarray.c > > ----------------------------------------------------------------------- > > Summary of changes: > src/backend/access/transam/varsup.c | 20 - > src/backend/access/transam/xact.c | 806 ++++------ > src/backend/commands/variable.c | 14 + > src/backend/nodes/outfuncs.c | 4 - > src/backend/optimizer/plan/createplan.c | 7 + > src/backend/pgxc/pool/execRemote.c | 2543 > +++++++++++++++---------------- > src/backend/pgxc/pool/pgxcnode.c | 309 +---- > src/backend/pgxc/pool/poolutils.c | 2 +- > src/backend/storage/ipc/ipci.c | 6 - > src/backend/storage/ipc/procarray.c | 164 +-- > src/backend/storage/lmgr/proc.c | 11 +- > src/backend/tcop/postgres.c | 8 - > src/backend/tcop/utility.c | 95 +- > src/backend/utils/error/elog.c | 15 - > src/backend/utils/mmgr/portalmem.c | 11 +- > src/include/access/xact.h | 17 +- > src/include/gtm/gtm_client.h | 3 +- > src/include/pgxc/execRemote.h | 16 +- > src/include/storage/lwlock.h | 1 - > src/include/storage/procarray.h | 4 - > 20 files changed, 1715 insertions(+), 2341 deletions(-) > > > hooks/post-receive > -- > Postgres-XC > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Postgres-xc-committers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-committers > -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com |
From: Pavan D. <pa...@us...> - 2012-03-06 13:14:08
|
Project "Postgres-XC". The branch, master has been updated via 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb (commit) via f5c981669460bcd696a266c9a336798b29769148 (commit) via 8efdf2b44e1cd42f255330abb1388a11fa0cec49 (commit) via 30dc60778733551b30c74344532152be6bab675f (commit) via 9f63e43eae0e69554fafd5b9032c662cf9ae120b (commit) via 8b7444f3c88104d0f078fd49514bc692d95ffed0 (commit) via c547574f4ba05ae21958b5a32b4742c84ce448c9 (commit) via 57e659829550d3e4c4dd82c7fef5cd3f20e94a48 (commit) via 9bf0a59a76844e4e673c871790e9e49375b27eb2 (commit) via 738e13b7a7945da99f06ad913a4fe570f3337abc (commit) from e1d299020b4f8cb04d11bb5f51bd86871e3e8881 (commit) - Log ----------------------------------------------------------------- http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=f5c981669460bcd696a266c9a336798b29769148 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8efdf2b44e1cd42f255330abb1388a11fa0cec49 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=30dc60778733551b30c74344532152be6bab675f commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9f63e43eae0e69554fafd5b9032c662cf9ae120b commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=8b7444f3c88104d0f078fd49514bc692d95ffed0 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=c547574f4ba05ae21958b5a32b4742c84ce448c9 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=57e659829550d3e4c4dd82c7fef5cd3f20e94a48 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=9bf0a59a76844e4e673c871790e9e49375b27eb2 commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=738e13b7a7945da99f06ad913a4fe570f3337abc commit 0fa52aaa33bede3d8cbc1c0fb678ac2c393a2edb Author: Pavan Deolasee <pav...@gm...> Date: Tue Mar 6 18:38:30 2012 +0530 Remove an assertion that checks for calling AbortTransaction on an already aborted transaction. We have seen this happening when a ROLLBACK statement is canceled by the client. We believe this is a PostgreSQL issue, but gets manifested by XC. We should discuss this further on the hackers list M src/backend/storage/ipc/procarray.c ----------------------------------------------------------------------- Summary of changes: src/backend/access/transam/varsup.c | 20 - src/backend/access/transam/xact.c | 806 ++++------ src/backend/commands/variable.c | 14 + src/backend/nodes/outfuncs.c | 4 - src/backend/optimizer/plan/createplan.c | 7 + src/backend/pgxc/pool/execRemote.c | 2543 +++++++++++++++---------------- src/backend/pgxc/pool/pgxcnode.c | 309 +---- src/backend/pgxc/pool/poolutils.c | 2 +- src/backend/storage/ipc/ipci.c | 6 - src/backend/storage/ipc/procarray.c | 164 +-- src/backend/storage/lmgr/proc.c | 11 +- src/backend/tcop/postgres.c | 8 - src/backend/tcop/utility.c | 95 +- src/backend/utils/error/elog.c | 15 - src/backend/utils/mmgr/portalmem.c | 11 +- src/include/access/xact.h | 17 +- src/include/gtm/gtm_client.h | 3 +- src/include/pgxc/execRemote.h | 16 +- src/include/storage/lwlock.h | 1 - src/include/storage/procarray.h | 4 - 20 files changed, 1715 insertions(+), 2341 deletions(-) hooks/post-receive -- Postgres-XC |
From: Amit K. <ami...@us...> - 2012-03-06 06:27:48
|
Project "Postgres-XC". The branch, master has been updated via e1d299020b4f8cb04d11bb5f51bd86871e3e8881 (commit) from 391b6973a55f32ec8a04a8e6871c245a06302bb1 (commit) - Log ----------------------------------------------------------------- http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=e1d299020b4f8cb04d11bb5f51bd86871e3e8881 commit e1d299020b4f8cb04d11bb5f51bd86871e3e8881 Author: Amit Khandekar <ami...@en...> Date: Tue Mar 6 11:57:02 2012 +0530 Fix for bug ID : 3459834 : plancache.sql: cache lookup failed for type 0 This issue was causing when RangeTblEntry->reltupdesc was printing attribute for which the column is marked as dropped. Removed reltupdesc field itself, because it is now found to be redundant. M src/backend/nodes/copyfuncs.c M src/backend/nodes/outfuncs.c M src/backend/nodes/readfuncs.c M src/backend/optimizer/plan/createplan.c M src/backend/parser/parse_relation.c M src/include/nodes/parsenodes.h M src/test/regress/serial_schedule ----------------------------------------------------------------------- Summary of changes: src/backend/nodes/copyfuncs.c | 2 - src/backend/nodes/outfuncs.c | 16 ---------- src/backend/nodes/readfuncs.c | 51 ------------------------------- src/backend/optimizer/plan/createplan.c | 16 +++++---- src/backend/parser/parse_relation.c | 2 - src/include/nodes/parsenodes.h | 1 - src/test/regress/serial_schedule | 2 +- 7 files changed, 10 insertions(+), 80 deletions(-) hooks/post-receive -- Postgres-XC |
From: Ashutosh B. <ash...@us...> - 2012-03-06 06:17:44
|
Project "Postgres-XC". The branch, master has been updated via 391b6973a55f32ec8a04a8e6871c245a06302bb1 (commit) from 37b44ed33e4f48165c1951298f52177f510b8cab (commit) - Log ----------------------------------------------------------------- http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=391b6973a55f32ec8a04a8e6871c245a06302bb1 commit 391b6973a55f32ec8a04a8e6871c245a06302bb1 Author: Ashutosh Bapat <ash...@en...> Date: Tue Mar 6 11:38:58 2012 +0530 Add the support for Fast Query Shipping (FQS), a method to identify whether a query can be sent to the datanode/s as it is for evaluation and do so if deemed fit. In such cases, we create a plan with a single RemoteQuery node corresponding to the query and avoid the planning phase on coordinator. A query tree walker analyses all the nodes in the query tree and finds out the conditions under which the query is shippable and detects presence of expressions which can not be evaluated on the datanode. It looks at the relations involved in the query and deducts whether JOINs between these relations can be evaluated on a single datanode. In create_remotequery_plan() if the table is distributed, the nodelist is reduced by looking at the qualifying conditions on the table. Function create_remotejoin_plan is modified to use the FQS logic to decide the shippability of JOIN. Adds testcases xc_FQS and xc_FQS_join to test the fast query shipping functionality and make it independent of cluster configuration. M src/backend/access/hash/hashfunc.c M src/backend/commands/explain.c M src/backend/optimizer/plan/createplan.c M src/backend/parser/analyze.c M src/backend/pgxc/locator/locator.c M src/backend/pgxc/plan/planner.c M src/include/pgxc/locator.h M src/include/pgxc/planner.h A src/test/regress/expected/xc_FQS.out A src/test/regress/expected/xc_FQS_join.out M src/test/regress/expected/xc_groupby.out M src/test/regress/expected/xc_having.out M src/test/regress/parallel_schedule M src/test/regress/serial_schedule A src/test/regress/sql/xc_FQS.sql A src/test/regress/sql/xc_FQS_join.sql M src/test/regress/sql/xc_groupby.sql M src/test/regress/sql/xc_having.sql ----------------------------------------------------------------------- Summary of changes: src/backend/access/hash/hashfunc.c | 4 + src/backend/commands/explain.c | 45 +- src/backend/optimizer/plan/createplan.c | 104 ++- src/backend/parser/analyze.c | 1 - src/backend/pgxc/locator/locator.c | 16 + src/backend/pgxc/plan/planner.c | 1712 ++++++++++++++++++++++------ src/include/pgxc/locator.h | 10 +- src/include/pgxc/planner.h | 35 +- src/test/regress/expected/xc_FQS.out | 1335 ++++++++++++++++++++++ src/test/regress/expected/xc_FQS_join.out | 552 ++++++++++ src/test/regress/expected/xc_groupby.out | 4 + src/test/regress/expected/xc_having.out | 51 +- src/test/regress/parallel_schedule | 2 +- src/test/regress/serial_schedule | 2 + src/test/regress/sql/xc_FQS.sql | 277 +++++ src/test/regress/sql/xc_FQS_join.sql | 155 +++ src/test/regress/sql/xc_groupby.sql | 6 + src/test/regress/sql/xc_having.sql | 5 + 18 files changed, 3856 insertions(+), 460 deletions(-) create mode 100644 src/test/regress/expected/xc_FQS.out create mode 100644 src/test/regress/expected/xc_FQS_join.out create mode 100644 src/test/regress/sql/xc_FQS.sql create mode 100644 src/test/regress/sql/xc_FQS_join.sql hooks/post-receive -- Postgres-XC |