Menu
▾
▴
postgres-xc-developers — Postgres-XC hackers and developers
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
(6) |
2
(10) |
3
(13) |
4
(1) |
5
|
|
6
|
7
(2) |
8
(4) |
9
(12) |
10
(1) |
11
|
12
|
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
|
20
|
21
|
22
(1) |
23
(2) |
24
(4) |
25
(3) |
26
|
|
27
|
28
|
29
|
30
(4) |
31
|
|
|
|
From: Koichi S. <koi...@gm...> - 2013-10-02 06:45:43
|
Okay, I will wait for your test result to commit it. --- Koichi Suzuki 2013/10/2 Michael Paquier <mic...@gm...> > On Wed, Oct 2, 2013 at 3:11 PM, Koichi Suzuki <koi...@gm...> > wrote: > > Are you testing them before committed or after then? > > > > BTW, koi...@gm... is obsolete (still alive though) and > please > > use koichi.dbms instead. > I have always been told to test things before committing them, not after :) > -- > Michael > |
|
From: Michael P. <mic...@gm...> - 2013-10-02 06:38:23
|
On Wed, Oct 2, 2013 at 3:11 PM, Koichi Suzuki <koi...@gm...> wrote: > Are you testing them before committed or after then? > > BTW, koi...@gm... is obsolete (still alive though) and please > use koichi.dbms instead. I have always been told to test things before committing them, not after :) -- Michael |
|
From: Koichi S. <koi...@gm...> - 2013-10-02 06:11:11
|
Are you testing them before committed or after then? BTW, koi...@gm... is obsolete (still alive though) and please use koichi.dbms instead. Regards; --- Koichi Suzuki 2013/10/2 Michael Paquier <mic...@gm...> > On Wed, Oct 2, 2013 at 10:33 AM, 鈴木 幸市 <ko...@in...> wrote: > > All the patches looks reasonable and can be applied to REL1_1_STABLE, as > well as master. > > > > Any more inputs? > Yep, I'd like to actually test them on a Solaris VM. > -- > Michael > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
|
From: Michael P. <mic...@gm...> - 2013-10-02 04:22:17
|
On Wed, Oct 2, 2013 at 10:33 AM, 鈴木 幸市 <ko...@in...> wrote: > All the patches looks reasonable and can be applied to REL1_1_STABLE, as well as master. > > Any more inputs? Yep, I'd like to actually test them on a Solaris VM. -- Michael |
|
From: 鈴木 幸市 <ko...@in...> - 2013-10-02 01:33:49
|
All the patches looks reasonable and can be applied to REL1_1_STABLE, as well as master. Any more inputs? --- Koichi Suzuki On 2013/10/02, at 8:58, Matt Warner <MW...@XI...> wrote: > Attached. > > Thanks! > > Matt > > -----Original Message----- > From: Michael Paquier [mailto:mic...@gm...] > Sent: Tuesday, October 01, 2013 4:57 PM > To: Matt Warner > Cc: 鈴木 幸市; Postgres-XC Developers; Koichi Suzuki > Subject: Re: [Postgres-xc-developers] Minor Fixes > > On Wed, Oct 2, 2013 at 8:06 AM, Matt Warner <MW...@xi...> wrote: >> I noticed that changes allowing XC to compile on Mac OS have been committed, >> but it doesn’t appear that the patches I supplied for Solaris have made it >> in. >> >> Is there something I’ve omitted that would make those patches more >> appealing? > Sorry I couldn't find those patches in my archives :(. My fault... > Could you send them on this thread? I promise I'll have a look at them > even if I don't have a Solaris platform at my disposition yet. This > gives a reason to have VM using it though. > -- > Michael > <solaris_makesgml-v1.patch><solaris_proxy_main-v2.patch><solaris_pgxcnode-v1.patch><solaris_sgml_Makefile-v1.patch><solaris_configure-v1.patch> |
|
From: Matt W. <MW...@XI...> - 2013-10-01 23:58:47
|
Attached. Thanks! Matt -----Original Message----- From: Michael Paquier [mailto:mic...@gm...] Sent: Tuesday, October 01, 2013 4:57 PM To: Matt Warner Cc: 鈴木 幸市; Postgres-XC Developers; Koichi Suzuki Subject: Re: [Postgres-xc-developers] Minor Fixes On Wed, Oct 2, 2013 at 8:06 AM, Matt Warner <MW...@xi...> wrote: > I noticed that changes allowing XC to compile on Mac OS have been committed, > but it doesn’t appear that the patches I supplied for Solaris have made it > in. > > Is there something I’ve omitted that would make those patches more > appealing? Sorry I couldn't find those patches in my archives :(. My fault... Could you send them on this thread? I promise I'll have a look at them even if I don't have a Solaris platform at my disposition yet. This gives a reason to have VM using it though. -- Michael |
|
From: Michael P. <mic...@gm...> - 2013-10-01 23:57:25
|
On Wed, Oct 2, 2013 at 8:06 AM, Matt Warner <MW...@xi...> wrote: > I noticed that changes allowing XC to compile on Mac OS have been committed, > but it doesn’t appear that the patches I supplied for Solaris have made it > in. > > Is there something I’ve omitted that would make those patches more > appealing? Sorry I couldn't find those patches in my archives :(. My fault... Could you send them on this thread? I promise I'll have a look at them even if I don't have a Solaris platform at my disposition yet. This gives a reason to have VM using it though. -- Michael |
|
From: Matt W. <MW...@XI...> - 2013-10-01 23:06:55
|
I noticed that changes allowing XC to compile on Mac OS have been committed, but it doesn’t appear that the patches I supplied for Solaris have made it in. Is there something I’ve omitted that would make those patches more appealing? Thanks! Matt From: Michael Paquier [mailto:mic...@gm...] Sent: Monday, August 05, 2013 6:25 AM To: 鈴木 幸市 Cc: Matt Warner; Postgres-XC Developers; Koichi Suzuki Subject: Re: [Postgres-xc-developers] Minor Fixes On Mon, Aug 5, 2013 at 10:09 PM, 鈴木 幸市 <ko...@in...<mailto:ko...@in...>> wrote: This depends on how serious the demand/usecase is and how works on it. Yes, you can work on it and you must have demanding usecase. I mean when 1.1GA is out, it's safer to concentrate on the master. This is a better place to work for Solaris. As 1.1 stable branch and master are already separated, what is the point of not committing what Matt has sent before it is forgotten? It is perfectly possible to continue the development work on master while improving the 1.1 beta state. IMO, I think that we should look at what Matt could send. -- Michael |
|
From: 鈴木 幸市 <ko...@in...> - 2013-10-01 09:34:51
|
Agree to remove #else .. . Assert is defined under #ifdef ASSERT_ENABLED internally and we don't have to worry about it. Without this symbol defined, Assert will be expanded to null and there's nothing bothering.
Regards;
---
Koichi Suzuki
On 2013/10/01, at 16:43, Ashutosh Bapat <ash...@en...<mailto:ash...@en...>> wrote:
We should move the Assert under #ifdef ASSERT_ENABLED as well the definition of old_outEnd. We should remove #else defining old_outEnd to handle->outEnd which is utterly wrong.
On Mon, Sep 30, 2013 at 12:15 PM, Koichi Suzuki <koi...@gm...<mailto:koi...@gm...>> wrote:
This change was made to eliminate a warning that old_outEnd is not used. To improve both, the patch would be as attached.
Regards;
---
Koichi Suzuki
2013/9/30 Abbas Butt <abb...@en...<mailto:abb...@en...>>
Hi,
The commit ae29a966d3286d4e85b3adf162d00f9b1e8b8eae made this change
@@ -1132,7 +1132,11 @@ pgxc_node_send_parse(PGXCNodeHandle * handle, const
char* statement,
/* message length */
int msgLen;
int cnt_params;
+#if 0
size_t old_outEnd = handle->outEnd;
+#else
+#define old_outEnd handle->outEnd
+#endif
which is incorrect. The purpose of the declaration and assignment is to
save the current value of handle->outEnd which is later changed in the
function.
This change makes the following assert in function pgxc_node_send_parse
Assert(old_outEnd + ntohl(msgLen) + 1 == handle->outEnd);
fail when the query
CREATE TABLE junk AS VALUES (1), (2);
is run.
This patch is required on master as well.
Regards
--
*Abbas*
Architect
Ph: 92.334.5100153
Skype ID: gabbasb
www.enterprisedb.co<http://www.enterprisedb.co/>
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB
Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community>and
more<http://www.enterprisedb.com/resources-community>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
|
|
From: Ashutosh B. <ash...@en...> - 2013-10-01 07:43:10
|
We should move the Assert under #ifdef ASSERT_ENABLED as well the definition of old_outEnd. We should remove #else defining old_outEnd to handle->outEnd which is utterly wrong. On Mon, Sep 30, 2013 at 12:15 PM, Koichi Suzuki <koi...@gm...>wrote: > This change was made to eliminate a warning that old_outEnd is not used. > To improve both, the patch would be as attached. > > Regards; > > --- > Koichi Suzuki > > > 2013/9/30 Abbas Butt <abb...@en...> > >> Hi, >> >> The commit ae29a966d3286d4e85b3adf162d00f9b1e8b8eae made this change >> @@ -1132,7 +1132,11 @@ pgxc_node_send_parse(PGXCNodeHandle * handle, const >> char* statement, >> /* message length */ >> int msgLen; >> int cnt_params; >> +#if 0 >> size_t old_outEnd = handle->outEnd; >> +#else >> +#define old_outEnd handle->outEnd >> +#endif >> >> which is incorrect. The purpose of the declaration and assignment is to >> save the current value of handle->outEnd which is later changed in the >> function. >> This change makes the following assert in function pgxc_node_send_parse >> Assert(old_outEnd + ntohl(msgLen) + 1 == handle->outEnd); >> fail when the query >> CREATE TABLE junk AS VALUES (1), (2); >> is run. >> >> This patch is required on master as well. >> >> Regards >> >> -- >> *Abbas* >> Architect >> >> Ph: 92.334.5100153 >> Skype ID: gabbasb >> www.enterprisedb.co >> <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/> >> * >> Follow us on Twitter* >> @EnterpriseDB >> >> Visit EnterpriseDB for tutorials, webinars, >> whitepapers<http://www.enterprisedb.com/resources-community>and >> more<http://www.enterprisedb.com/resources-community> >> >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most >> from >> the latest Intel processors and coprocessors. See abstracts and register > >> >> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk >> _______________________________________________ >> Postgres-xc-developers mailing list >> Pos...@li... >> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >> >> > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company |
|
From: 鈴木 幸市 <ko...@in...> - 2013-10-01 00:58:21
|
Hmmm. I don't see clear background that CLEAN CONNECTION should have its event trigger either. --- Koichi Suzuki On 2013/09/30, at 18:53, Michael Paquier <mic...@gm...> wrote: > On Mon, Sep 30, 2013 at 4:19 PM, 鈴木 幸市 <ko...@in...> wrote: >> Do you agree not to support event triggers because it does support only a subset of CREATE/ALTER/DROP or XC architecture needs extra improvement? > Supporting event triggers would be a nice thing, just I don't see why > it would be necessary for CLEAN CONNECTION. > -- > Michael > |
2 messages has been excluded from this view by a project administrator.
