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
|
3
|
4
|
5
(3) |
6
(1) |
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
(3) |
19
|
20
(2) |
21
(1) |
22
|
23
|
24
(4) |
25
(7) |
26
(1) |
27
(3) |
28
(3) |
29
|
30
|
|
|
|
|
|
|
From: Abbas B. <ga...@us...> - 2013-06-06 02:32:30
|
Project "Postgres-XC". The branch, master has been updated via e688e8c9c9e02016fbfb0f8c6fb1c45a81b4373d (commit) from 4f610fa74394eb379a3baf3fdd0ea9c722ead3b2 (commit) - Log ----------------------------------------------------------------- http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=commitdiff;h=e688e8c9c9e02016fbfb0f8c6fb1c45a81b4373d commit e688e8c9c9e02016fbfb0f8c6fb1c45a81b4373d Author: Abbas <abb...@en...> Date: Thu Jun 6 07:08:13 2013 +0500 Fix handling of number of tuples processed Problem: Currently the number of tuples processed is updated in both HandleCommandComplete and ExecInsert/Update/Delete. In HandleCommandComplete() it gets it from the command tag returned from the datanode i.e. INSERT 0 2, UPDATE 5 and likewise. And then it updates estate->es_processed. But it does this only for FQS. For non-FQS, in ExecInsert/Update, it is just incremented by 1. So if a trigger function skips one row on datanode, the command tag returned from datanode is INSERT 0 0. But still in ExecInsert() increments the row count. Solution: Add a new field RemoteQueryState->rqs_processed, which is updated in HandleCommandComplete(). Then it is used in ExecInsert/Update/Delete() for non-FQS, and in RemoteQueryNext() for FQS. Patch By Amit Khandekar I just reviewed the patch, did a minor fix and committed the patch. M src/backend/executor/nodeModifyTable.c M src/backend/pgxc/pool/execRemote.c M src/include/pgxc/execRemote.h M src/test/regress/expected/xc_returning.out M src/test/regress/expected/xc_trigship.out M src/test/regress/sql/xc_returning.sql M src/test/regress/sql/xc_trigship.sql ----------------------------------------------------------------------- Summary of changes: src/backend/executor/nodeModifyTable.c | 79 ++++--------------------- src/backend/pgxc/pool/execRemote.c | 86 +++++++++++++++++----------- src/include/pgxc/execRemote.h | 4 +- src/test/regress/expected/xc_returning.out | 45 ++++++++++++++ src/test/regress/expected/xc_trigship.out | 55 ++++++++++++++++++ src/test/regress/sql/xc_returning.sql | 39 +++++++++++++ src/test/regress/sql/xc_trigship.sql | 1 + 7 files changed, 205 insertions(+), 104 deletions(-) hooks/post-receive -- Postgres-XC |