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
|
8
|
9
|
10
|
11
|
12
|
13
(2) |
14
(3) |
15
|
16
|
17
|
18
(2) |
19
(1) |
20
(3) |
21
|
22
(5) |
23
|
24
|
25
(1) |
26
|
27
|
28
|
29
(1) |
30
|
31
|
|
|
|
|
|
|
From: Mason S. <mas...@en...> - 2010-10-14 15:14:17
|
On 10/14/10 3:30 AM, mei le wrote: > Dears, > Postgres-xc version 0.9.2 has error process at the end of funcion > "ExecRemoteQuery" but such a part was deleted by later patch.In > postgres-xc 0.9.2, if I create a table on one datanode, I can't create > table on other datanodes by executing create table statment on > Coordinator, but the newest code can create table on other datanodes > by executiong same statement on Coordinator.I think the former version > is more appropriate than the newest code. Could you give me some > explains on this issue? > Thanks. > > Truely, > > Benny > > Benny, I am sorry, can you please explain again, I think I do not understand. In Postgres-XC, when you create a table, you do it against a Coordinator, and not a Data Node. The Coordinator will automatically create the table on the Data Nodes for you. It should be this way for both 0.9.2 and the latest code in the git repository. Please let me know if I misunderstood something. Thanks, Mason > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2& L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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. |
From: mei le <lem...@ya...> - 2010-10-14 07:31:10
|
Dears, Postgres-xc version 0.9.2 has error process at the end of funcion "ExecRemoteQuery" but such a part was deleted by later patch.In postgres-xc 0.9.2, if I create a table on one datanode, I can't create table on other datanodes by executing create table statment on Coordinator, but the newest code can create table on other datanodes by executiong same statement on Coordinator.I think the former version is more appropriate than the newest code. Could you give me some explains on this issue? Thanks. Truely, Benny |
From: Mason S. <mas...@en...> - 2010-10-14 00:10:52
|
Thanks, I will look at it soon more carefully. A manual checkpoint should not occur too often, so I am not that concerned about efficiency for this case. Can the other code you did be used for other cases, too? Thanks, Mason On 10/13/10 5:35 AM, mei le wrote: > Dears, > I made two patches for bug > https://sourceforge.net/tracker/?limit=25&func=&group_id=311227&atid=1310232&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=1&category=&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter&mass_category=&mass_priority=&mass_resolution=&mass_assignee=&mass_artgroup=&mass_status=&mass_cannedresponse= > <https://sourceforge.net/tracker/?limit=25&func=&group_id=311227&atid=1310232&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=1&category=&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter&mass_category=&mass_priority=&mass_resolution=&mass_assignee=&mass_artgroup=&mass_status=&mass_cannedresponse=> > 3076224 checkpoint command causes seg fault > 3010262 Primary Key in CREATE TABLE > 3013984 Sequence scope > 3013562 Multiple insert not possible > The first one is the most simple method to solve the bug, but it may > lower efficency. So, I made second one which did special process for > checkpoint which doesn't need transaction process. > Looking forward your kindly reply. > > Truely, > > Benny > --- *10年9月30日,周四, Mason Sharp /<mas...@en...>/* > 写道: > > > 发件人: Mason Sharp <mas...@en...> > 主题: tasks > 收件人: "mei le" <lem...@ya...> > 抄送: ""03:鈴木(幸)様(DI)"" <ko...@in...> > 日期: 2010年9月30日,周四,下午4:46 > > I understand you and your friends are busy for a while. > > If you would like to get involved, once you have more time later, > here are some tasks that might be some good ones to start with, in > approximate order of what makes sense to work on. > > > > Bugs > > https://sourceforge.net/tracker/?limit=25&func=&group_id=311227&atid=1310232&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=1&category=&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter&mass_category=&mass_priority=&mass_resolution=&mass_assignee=&mass_artgroup=&mass_status=&mass_cannedresponse= > <https://sourceforge.net/tracker/?limit=25&func=&group_id=311227&atid=1310232&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=1&category=&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter&mass_category=&mass_priority=&mass_resolution=&mass_assignee=&mass_artgroup=&mass_status=&mass_cannedresponse=> > > 3076224 checkpoint command causes seg fault > 3010262 Primary Key in CREATE TABLE > 3013984 Sequence scope > 3013562 Multiple insert not possible > > > > Features > > https://sourceforge.net/tracker/?group_id=311227&atid=1310235 > <https://sourceforge.net/tracker/?group_id=311227&atid=1310235> > > 3000104 COPY TO with SELECT > 3014003 Pooler Request Queuing > 3014002 Pooler should shrink > 3022406 Safer Hash Distribution to Data Nodes > > > Thanks, > > Mason > > -- Mason Sharp > EnterpriseDB Corporation > The Enterprise Postgres Company > > > 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. > > -- Mason Sharp EnterpriseDB Corporation The Enterprise Postgres Company 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. |