From: mei le <lem...@ya...> - 2010-09-19 05:13:43
|
Dears : This is Benny ,a postgraduate for DBMS from DUTchina. I have studied postgreSQL for a long time. And I have always kept close eye on postgreSQL cluster solutions such as PGCluster-2 and GridSQL etc. After postgres-xc released, I have learned much about it. It's a great cluster frame. I have been reading postgres-xc source code recently. Reading PostgresSQL code, I always like to read README under relative directory, which can make me learn more knowledge on its relative functions. But when I scan postgres-xc code which was freshly added, I can't find any README to introduce the summary or relative knowledge. I think README is very important to an open source code. I don't know why postgres-xc ignores README files .Could we add the README files later? Truly yours, Benny |
From: Koichi S. <koi...@gm...> - 2010-09-20 04:15:59
|
Benny, Thank you very much for the suggestion. Yes, I understand the README is not rich. Instead, we have "architecture" document which you can download separately, as well as other manual and guidelines. Could you try these documents? Especially, I made "architecture" document as a separate one because XC internal is not simple to understand and I thought usual document with graphics and tables will be more helpful. Your advice is very valuable. I'll be waiting for your further advice. Thank you very much; ---------- Koichi Suzuki 2010/9/19 mei le <lem...@ya...> > Dears : > > This is Benny ,a postgraduate for DBMS from DUTchina. I have > studied postgreSQL for a long time. And I have always kept close eye on > postgreSQL cluster solutions such as PGCluster-2 and GridSQL etc. After > postgres-xc released, I have learned much about it. It's a great cluster > frame. I have been reading postgres-xc source code recently. > > > > Reading PostgresSQL code, I always like to read README under > relative directory, which can make me learn more knowledge on its relative > functions. But when I scan postgres-xc code which was freshly added, I can't > find any README to introduce the summary or relative knowledge. I think > README is very important to an open source code. I don't know why > postgres-xc ignores README files .Could we add the README files later? > > > > > Truly yours, > > > > Benny > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > |
From: Mason S. <mas...@en...> - 2010-09-20 13:55:34
|
Benny, An additional comment- In the source code, most of the changes compared to PostgreSQL are below src/backend/pgxc. These are all new files. You can look through and read comments. In addition, changes to existing PostgreSQL modules can be easily found by searching for the string PGXC, so you can see what changed and why. Thanks, Mason On 9/20/10 12:15 AM, Koichi Suzuki wrote: > Benny, > > Thank you very much for the suggestion. Yes, I understand the > README is not rich. Instead, we have "architecture" document which > you can download separately, as well as other manual and guidelines. > > Could you try these documents? Especially, I made "architecture" > document as a separate one because XC internal is not simple to > understand and I thought usual document with graphics and tables will > be more helpful. > > Your advice is very valuable. I'll be waiting for your further advice. > > Thank you very much; > ---------- > Koichi Suzuki > > > 2010/9/19 mei le <lem...@ya... > <mailto:lem...@ya...>> > > Dears : > > This is Benny ,a postgraduate for DBMS from DUTchina. I have > studied postgreSQL for a long time. And I have always kept close > eye on postgreSQL cluster solutions such as PGCluster-2 and > GridSQL etc. After postgres-xc released, I have learned much about > it. It's a great cluster frame. I have been reading postgres-xc > source code recently. > > Reading PostgresSQL code, I always like to read README > under relative directory, which can make me learn more knowledge > on its relative functions. But when I scan postgres-xc code which > was freshly added, I can't find any README to introduce the > summary or relative knowledge. I think README is very important to > an open source code. I don't know why postgres-xc ignores README > files .Could we add the README files later? > > > Truly yours, > > Benny > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > <mailto:Pos...@li...> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > > > _______________________________________________ > 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. |