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
(1) |
2
|
3
(6) |
4
(8) |
5
(9) |
6
|
|
7
|
8
(6) |
9
(4) |
10
(5) |
11
(2) |
12
|
13
|
|
14
|
15
(1) |
16
(2) |
17
(5) |
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
|
28
|
29
(2) |
30
(7) |
31
(11) |
|
|
|
|
From: Koichi S. <koi...@gm...> - 2011-08-09 03:03:37
|
Good. So let's discuss it at the next regular progress MTG ---------- Koichi Suzuki 2011/8/9 Michael Paquier <mic...@gm...>: > Yes I think so, I may need input about what kind of restrictions they expect > for their applications. > For example, if they decide that we should only provide support for only FOR > EACH ROW or FOR EACH STATEMENT, this may drastically change the design for > triggers. > > On Tue, Aug 9, 2011 at 11:54 AM, Koichi Suzuki <koi...@gm...> wrote: >> >> Yes, I agree to want for some more input. Do you think we should >> wait for NTT people to be back to the office? >> ---------- >> Koichi Suzuki >> >> >> >> 2011/8/9 Michael Paquier <mic...@gm...>: >> > OK, this warning evaluation could be done a trigger creation. >> > Btw, let's wait for more input. I'd prefer have some more data before >> > doing >> > any support for triggers. >> > >> > -- >> > Michael Paquier >> > http://michael.otacoo.com >> > > > > > -- > Michael Paquier > http://michael.otacoo.com > |
|
From: Michael P. <mic...@gm...> - 2011-08-09 02:58:23
|
Yes I think so, I may need input about what kind of restrictions they expect for their applications. For example, if they decide that we should only provide support for only FOR EACH ROW or FOR EACH STATEMENT, this may drastically change the design for triggers. On Tue, Aug 9, 2011 at 11:54 AM, Koichi Suzuki <koi...@gm...> wrote: > Yes, I agree to want for some more input. Do you think we should > wait for NTT people to be back to the office? > ---------- > Koichi Suzuki > > > > 2011/8/9 Michael Paquier <mic...@gm...>: > > OK, this warning evaluation could be done a trigger creation. > > Btw, let's wait for more input. I'd prefer have some more data before > doing > > any support for triggers. > > > > -- > > Michael Paquier > > http://michael.otacoo.com > > > -- Michael Paquier http://michael.otacoo.com |
|
From: Koichi S. <koi...@gm...> - 2011-08-09 02:54:26
|
Yes, I agree to want for some more input. Do you think we should wait for NTT people to be back to the office? ---------- Koichi Suzuki 2011/8/9 Michael Paquier <mic...@gm...>: > OK, this warning evaluation could be done a trigger creation. > Btw, let's wait for more input. I'd prefer have some more data before doing > any support for triggers. > > -- > Michael Paquier > http://michael.otacoo.com > |
|
From: Michael P. <mic...@gm...> - 2011-08-09 02:33:39
|
OK, this warning evaluation could be done a trigger creation. Btw, let's wait for more input. I'd prefer have some more data before doing any support for triggers. -- Michael Paquier http://michael.otacoo.com |
