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
|
2
|
3
|
4
|
5
|
6
|
7
(3) |
8
|
9
(1) |
10
(1) |
11
(10) |
12
(4) |
13
(8) |
14
(2) |
15
|
16
|
17
(1) |
18
(2) |
19
(1) |
20
|
21
(1) |
22
|
23
|
24
|
25
(1) |
26
(3) |
27
(2) |
28
(6) |
29
(1) |
30
|
31
|
|
|
|
|
|
From: xiong w. <wan...@gm...> - 2011-01-14 01:59:57
|
Hi Andrei, Thank you very much. I understand now. Regards, Benny 2011/1/13 Andrei.Martsinchyk <and...@en...>: > Benny, > > OK, the distributed constraint restriction still in force. > Partitioning of master and slave tables should guarantee that if > master record ever presents in the table it must be on the same data > node as the slave record. Constraint checker only sees local data > node, it can not look up other datanodes. > > 2011/1/13 xiong wang <wan...@gm...>: >> Hi, >> I am sorry that I took a wrong case as an example. >> The right example is like: >> postgres=# create table xyz(x int, y int, foreign key(y) references >> shench(a)) distribute by hash(x);//not by hash(a) >> ERROR: Hash distributed table must include distribution column in index >> >> My question is why hash distributed key "x" must be included in foreign keys. >> >> Many thanks for your reply. >> >> Regards, >> Benny >> >> 2011/1/13 Andrei.Martsinchyk <and...@en...>: >>> Benny, >>> >>> The column specified in hash() clause must be from table being >>> created. The specified (a) column is from other table. It looks like >>> it just output incorrect error message. >>> The note about distributed constraint is correct. >>> In your example one of two conditions must be met: >>> Table xyz must be hash distributed by y AND shench table must be hash >>> distributed by a AND columns y and a must be of the same data type; >>> or >>> shench table must be replicated. >>> >>> 2011/1/13 Koichi Suzuki <ko...@in...>: >>>> Unfortunately, reference integrity is not fully supported by XC yet, >>>> because we have to check existing of the matching rows in different data >>>> nodes, which is not simple, as in the case of global unique constraint >>>> for non-distribution columns. >>>> >>>> So I think this is one of the issue we have. >>>> >>>> Any further thoughts? >>>> >>>> --- >>>> Koichi >>>> >>>> (2011年01月13日 15:53), xiong wang wrote: >>>>> Dears, >>>>> >>>>> When We are fixing the bug relative with the foreign key, there is >>>>> something we are confused. The problem as follows: >>>>> postgres=# create table xyz(x int, y int, foreign key(y) references >>>>> shench(a)) distribute by hash(a); >>>>> ERROR: Hash distributed table must include distribution column in index >>>>> >>>>> I don't know why Hash distributed column must be included in foreign >>>>> constraint. Could you explain something? >>>>> >>>>> Thanks a lot. >>>>> >>>>> Regards, >>>>> Benny >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Protect Your Site and Customers from Malware Attacks >>>>> Learn about various malware tactics and how to avoid them. Understand >>>>> malware threats, the impact they can have on your business, and how you >>>>> can protect your company and customers by using code signing. >>>>> http://p.sf.net/sfu/oracle-sfdevnl >>>>> _______________________________________________ >>>>> Postgres-xc-developers mailing list >>>>> Pos...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Protect Your Site and Customers from Malware Attacks >>>> Learn about various malware tactics and how to avoid them. Understand >>>> malware threats, the impact they can have on your business, and how you >>>> can protect your company and customers by using code signing. >>>> http://p.sf.net/sfu/oracle-sfdevnl >>>> _______________________________________________ >>>> Postgres-xc-developers mailing list >>>> Pos...@li... >>>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers >>>> >>> >>> >>> >>> -- >>> Andrei Martsinchyk >>> >>> EntepriseDB Corporation >>> The Enterprise Postgres Company >>> >>> Website: www.enterprisedb.com >>> EnterpriseDB Blog: http://blogs.enterprisedb.com/ >>> Follow us on Twitter: http://www.twitter.com/enterprisedb >>> >>> This e-mail message (and any attachment) is intended for the use of >>> the individual or entity to whom it is addressed. This message >>> contains information from EnterpriseDB Corporation that may be >>> privileged, confidential, or exempt from disclosure under applicable >>> law. If you are not the intended recipient or authorized to receive >>> this for the intended recipient, any use, dissemination, distribution, >>> retention, archiving, or copying of this communication is strictly >>> prohibited. If you have received this e-mail in error, please notify >>> the sender immediately by reply e-mail and delete this message. >>> >> > > > > -- > Andrei Martsinchyk > > EntepriseDB Corporation > The Enterprise Postgres Company > > Website: www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of > the individual or entity to whom it is addressed. This message > contains information from EnterpriseDB Corporation that may be > privileged, confidential, or exempt from disclosure under applicable > law. If you are not the intended recipient or authorized to receive > this for the intended recipient, any use, dissemination, distribution, > retention, archiving, or copying of this communication is strictly > prohibited. If you have received this e-mail in error, please notify > the sender immediately by reply e-mail and delete this message. > |