You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(17) |
Jun
(3) |
Jul
|
Aug
|
Sep
(8) |
Oct
(18) |
Nov
(51) |
Dec
(74) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(47) |
Feb
(44) |
Mar
(44) |
Apr
(102) |
May
(35) |
Jun
(25) |
Jul
(56) |
Aug
(69) |
Sep
(32) |
Oct
(37) |
Nov
(31) |
Dec
(16) |
2012 |
Jan
(34) |
Feb
(127) |
Mar
(218) |
Apr
(252) |
May
(80) |
Jun
(137) |
Jul
(205) |
Aug
(159) |
Sep
(35) |
Oct
(50) |
Nov
(82) |
Dec
(52) |
2013 |
Jan
(107) |
Feb
(159) |
Mar
(118) |
Apr
(163) |
May
(151) |
Jun
(89) |
Jul
(106) |
Aug
(177) |
Sep
(49) |
Oct
(63) |
Nov
(46) |
Dec
(7) |
2014 |
Jan
(65) |
Feb
(128) |
Mar
(40) |
Apr
(11) |
May
(4) |
Jun
(8) |
Jul
(16) |
Aug
(11) |
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(16) |
2015 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(4) |
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
1
(10) |
2
(18) |
3
(1) |
4
|
5
(15) |
6
(16) |
7
(11) |
8
(17) |
9
(7) |
10
(6) |
11
(1) |
12
(6) |
13
(4) |
14
(8) |
15
(3) |
16
(3) |
17
|
18
|
19
(8) |
20
(10) |
21
(12) |
22
(5) |
23
(3) |
24
|
25
|
26
(2) |
27
(2) |
28
(1) |
29
(2) |
30
(5) |
31
(1) |
From: Nikhil S. <ni...@st...> - 2013-08-10 17:19:09
|
Hi, Have a Query about ExecRemoteQuery. The logic seems to have been modeled after ExecMaterial. ISTM, that it should have been modeled after ExecScan because we fetch tuples, and those which match the qual should be sent up. ExecMaterial is for materializing and collecting and storing tuples. Can anyone explain? The reason for asking this is I am suspecting a big memory leak in this code path. We are not using any expression context nor we are freeing up tuples as we scan for the one which qualifies. Regards, Nikhils -- StormDB - http://www.stormdb.com The Database Cloud |
From: Abbas B. <abb...@en...> - 2013-08-10 06:05:05
|
PFA revised patch. On Fri, Aug 9, 2013 at 9:31 AM, Masataka Saito <pg...@gm...> wrote: > It will work. But it took a bit time to understand that > selectSQL("testdate order by i", "dt")) is expanded to "SELECT dt FROM > testdate order by i" because the first argument name of selectSQL is > "table". > You'd better use selectSQL (String table, String columns, String > where, String other) rather than selectSQL(String table, String > columns). > > On Thu, Aug 8, 2013 at 6:31 PM, Abbas Butt <abb...@en...> wrote: >> Hi, >> PFA patch to fix date tests needing order by. >> >> -- >> Abbas >> Architect >> >> Ph: 92.334.5100153 >> Skype ID: gabbasb >> www.enterprisedb.com >> >> Follow us on Twitter >> @EnterpriseDB >> >> Visit EnterpriseDB for tutorials, webinars, whitepapers and more >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> -- -- Abbas Architect Ph: 92.334.5100153 Skype ID: gabbasb www.enterprisedb.com Follow us on Twitter @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers and more |
From: Abbas B. <abb...@en...> - 2013-08-10 05:58:07
|
On Fri, Aug 9, 2013 at 2:19 PM, Masataka Saito <pg...@gm...> wrote: > On Thu, Aug 8, 2013 at 9:41 PM, Abbas Butt <abb...@en...> wrote: >> Hi, >> PFA patch to fix an XC limitation that update of a replicated table >> created with oids cannot be based on oids. > > When did you change distribution rule to REPLICATION from ROUNDROBIN? > I lost your patch. > >> i.e. this update supposed to fail >> update rep_table_with_oids set colum = $1 where oid=$2 >> saying >> ERROR : Write to replicated table returned different results from the Datanodes >> >> The reason is that we would select oid from the primary datanode and >> that particular oid will not be there on the rest of the datanodes. >> The patch comments explain the complete scenario in detail. >> >> With this patch the JDBC regression runs without any failures or >> errors on my machine. >> Strangely I did not have to change any thing on the server side. > > What do you experience the strangeness of? I meant that none of the tests failing in JDBC test suite require any change in the server, when this work was started we thought JDBC test suite might uncover some bug in the server. > Your patch eliminated "oid" column from the selection, therefore, > UPDATE query does not contain "oid" anymore. I think it is > straightforward. > > Regards. > >> >> -- >> Abbas >> Architect >> >> Ph: 92.334.5100153 >> Skype ID: gabbasb >> www.enterprisedb.com >> >> Follow us on Twitter >> @EnterpriseDB >> >> Visit EnterpriseDB for tutorials, webinars, whitepapers and more >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> -- -- Abbas Architect Ph: 92.334.5100153 Skype ID: gabbasb www.enterprisedb.com Follow us on Twitter @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers and more |
From: Abbas B. <abb...@en...> - 2013-08-10 05:49:36
|
PFA revised patch On Fri, Aug 9, 2013 at 9:47 AM, Masataka Saito <pg...@gm...> wrote: > My comment is same as the one for 10_1_date. patch. > > On Thu, Aug 8, 2013 at 6:32 PM, Abbas Butt <abb...@en...> wrote: >> Hi, >> PFA patch to fix time tests needing order by. >> >> -- >> Abbas >> Architect >> >> Ph: 92.334.5100153 >> Skype ID: gabbasb >> www.enterprisedb.com >> >> Follow us on Twitter >> @EnterpriseDB >> >> Visit EnterpriseDB for tutorials, webinars, whitepapers and more >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> -- -- Abbas Architect Ph: 92.334.5100153 Skype ID: gabbasb www.enterprisedb.com Follow us on Twitter @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers and more |
From: Abbas B. <abb...@en...> - 2013-08-10 05:41:32
|
PFA revised patch On Fri, Aug 9, 2013 at 11:32 AM, Masataka Saito <pg...@gm...> wrote: > I think "order by" in runInfinityTests is unnecessary. > > On Thu, Aug 8, 2013 at 6:33 PM, Abbas Butt <abb...@en...> wrote: >> Hi, >> PFA path to fix time-stamp tests needing order by >> >> -- >> Abbas >> Architect >> >> Ph: 92.334.5100153 >> Skype ID: gabbasb >> www.enterprisedb.com >> >> Follow us on Twitter >> @EnterpriseDB >> >> Visit EnterpriseDB for tutorials, webinars, whitepapers and more >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite! >> It's a free troubleshooting tool designed for production. >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> -- -- Abbas Architect Ph: 92.334.5100153 Skype ID: gabbasb www.enterprisedb.com Follow us on Twitter @EnterpriseDB Visit EnterpriseDB for tutorials, webinars, whitepapers and more |