postgres-xc-general Mailing List for Postgres-XC (Page 60)

pgcrypto looks to work fine.   Obviously, it is not recommended to
encrypt distribution key, where we don't have good optimization.

Here's my result.

Enjoy;
----
Koichi

----8<------------------------8<------------
postgres=# create extension pgcrypto;
CREATE EXTENSION
postgres=# create table test (id int, name bytea);
CREATE TABLE
postgres=# insert into test select 1, encrypt(convert_to('Suzuki',
'UTF8'), 'pass'::bytea, 'aes');
INSERT 0 1
postgres=# insert into test select 2, pgp_sym_encrypt('Sato', 'pass');
INSERT 0 1
postgres=# insert into test select 3, pgp_sym_encrypt('Sato', 'pass');
INSERT 0 1
postgres=# select * from test;
 id |
    name
----+------------------------------------------------------------------------------------------------------------------------------------------------
  1 | \x42a2c9e81526133e031336b8a09a3ae8
  2 | \xc30d0407030285360772296ea94e78d2350126b86572a89a4f054fb95eb0b8ab86b214e66571469460a469b740f26c3465e19f17500703e75e06378bc4b75b37f053befad44a
  3 | \xc30d040703024a9931a54cde6b6f60d235011bdbf887c8a0cb2e122ed034101ef64b3d5fb7d25cbff91dd82661de665651d92c0c1ee7d6672139ef7e59b767bb90612ab71bef
(3 rows)

postgres=# SELECT id, convert_from(decrypt(name, 'pass'::bytea,
'aes'), 'UTF8') FROM test where id = 1;
 id | convert_from
----+--------------
  1 | Suzuki
(1 row)

postgres=# SELECT id, pgp_sym_decrypt(name,'pass') FROM test WHERE id IN (2,3);
 id | pgp_sym_decrypt
----+-----------------
  3 | Sato
  2 | Sato
(2 rows)

postgres=# create table test1 (id varchar, name bytea);
CREATE TABLE
postgres=# insert into test1 values (pgp_sym_encrypt('1', 'pass'),
pgp_sym_encrypt('Suzuki', 'pass'));
INSERT 0 1
postgres=# select * from test1;
                                                                    id
                                                                   |

name
------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------
 \xc30d0407030233ffc6b915c7908d62d23201980e846bcfbf772c43ae7bb5c9476da716fe80dd2149e81aaa2353767bb5402af7fa54eb8b498ea21de58a58e8ca697229
| \xc30d040703020169a4462ef5f63d65d2370108b2e0dea578142f63e416989a95e19663605c7f035b54074d6f190e704e7bf75b651c6dfa6091667a8242fcd91ae60384bf0ec0c4c6
(1 row)

postgres=# select pgp_sym_decrypt(id::bytea, 'pass'),
pgp_sym_decrypt(name::bytea, 'pass') from test1;
 pgp_sym_decrypt | pgp_sym_decrypt
-----------------+-----------------
 1               | Suzuki
(1 row)

postgres=# select pgp_sym_decrypt(id::bytea, 'pass'),
pgp_sym_decrypt(name::bytea, 'pass') from test1 where
pgp_sym_decrypt(id::bytea, 'pass') = '1';
 pgp_sym_decrypt | pgp_sym_decrypt
-----------------+-----------------
 1               | Suzuki
(1 row)

postgres=#
---->8------------------------>8------------


2012/7/26 Aris Setyawan <ari...@gm...>:
> Hi All,
>
> Is "Additional Supplied Modules" supported in XC cluster (hstore,
> pgcrypto, etc..)?
>
> -thanks
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

Yes, namely yes.   May need to share the test.

Here's my test of hstore.   It looks to run.   The example was from
http://d.hatena.ne.jp/rudi/20120330/1333120115 (originally in
Japanese).   Of course, "products" table is distributed by hash on id.

Regards;
---
Koichi

--------------8<-------------------------8<-----------------
[koichi@willey:pgxc]$ psql -p 20004 postgres
psql (PGXC 1.1devel, based on PG 9.2devel)
Type "help" for help.

postgres=# create extension hstore;
WARNING:  => is deprecated as an operator name
DETAIL:  This name may be disallowed altogether in future versions of
PostgreSQL.
CREATE EXTENSION
postgres=# CREATE TABLE products (id serial PRIMARY KEY, name varchar,
attrubutes hstore);
NOTICE:  CREATE TABLE will create implicit sequence "products_id_seq"
for serial column "products.id"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"products_pkey" for table "products"
CREATE TABLE
postgres=# INSERT INTO products (name, attributes) VALUES
postgres-# ('Geel Love: A Novel',
postgres(# 'author => "Katherine Dunn",
postgres'# pages => 368,
postgres'# category => fiction'
postgres(# );
ERROR:  column "attributes" of relation "products" does not exist
LINE 1: INSERT INTO products (name, attributes) VALUES
                                    ^
postgres=# drop table products
postgres-# ;
DROP TABLE
postgres=# CREATE TABLE products (
postgres(#   id serial PRIMARY KEY,
postgres(#   name varchar,
postgres(#   attributes hstore
postgres(# );
NOTICE:  CREATE TABLE will create implicit sequence "products_id_seq"
for serial column "products.id"
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
"products_pkey" for table "products"
CREATE TABLE
postgres=# INSERT INTO products (name, attributes) VALUES (
postgres(#   'Geek Love: A Novel',
postgres(#   'author    => "Katherine Dunn",
postgres'#    pages     => 368,
postgres'#    category  => fiction'
postgres(#   );
INSERT 0 1
postgres=# SELECT name as device
postgres-# FROM products
postgres-# WHERE attributes->'category' = 'fiction';
       device
--------------------
 Geek Love: A Novel
(1 row)

postgres=# SELECT name, attributes->'pages'
postgres-#   FROM products
postgres-#   WHERE attributes ? 'pages';
        name        | ?column?
--------------------+----------
 Geek Love: A Novel | 368
(1 row)

postgres=# CREATE INDEX product_manufacturer
postgres-# ON products ((products.attributes->'manufacturer'));
CREATE INDEX
postgres=#
--------->8--------------------------->8-------------------------

2012/7/26 Michael Paquier <mic...@gm...>:
>
>
> On Thu, Jul 26, 2012 at 3:09 PM, Aris Setyawan <ari...@gm...> wrote:
>>
>> Hi All,
>>
>> Is "Additional Supplied Modules" supported in XC cluster (hstore,
>> pgcrypto, etc..)?
>
> Normally yes. I tested some of them and they should work. There might be
> exceptions though.
> --
> Michael Paquier
> http://michael.otacoo.com
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

On Thu, Jul 26, 2012 at 3:30 PM, Aris Setyawan <ari...@gm...> wrote:

> > Normally yes. I tested some of them and they should work. There might be
> exceptions though.
>
> Can I rely on the current 1.0 XC's documentation to find out if one
> module is supported?
>
Yes you can. They may be some mistakes in the documentation as there are
not so many people maintaining and correcting it.
So if you find anything that does not correspond, feel free to report that
on this thread.

Thanks,
-- 
Michael Paquier
http://michael.otacoo.com

On Thu, Jul 26, 2012 at 3:09 PM, Aris Setyawan <ari...@gm...> wrote:

> Hi All,
>
> Is "Additional Supplied Modules" supported in XC cluster (hstore,
> pgcrypto, etc..)?
>
Normally yes. I tested some of them and they should work. There might be
exceptions though.
-- 
Michael Paquier
http://michael.otacoo.com

Hi All,

Is "Additional Supplied Modules" supported in XC cluster (hstore,
pgcrypto, etc..)?

-thanks

It seems not reasonable to ask single license to all the Postgres-XC documents.    License could be different from document to document, especially those written by individuals.

As Joshua mentioned, maybe we can ask specific license to web site or Wiki contents and contributors to such contents should agree on this.

Creative commons looks looks okay.   ShareAlike, maybe no objection.   Then commercial or non-commercial?   As I mentioned before, I'm not sure what corner case "commercial" implies.    Fair use is allowd unconditionally.    So I think we can begin with non-commercial.

Any more inputs?
---
Koichi Suzuki

On Tue, 24 Jul 2012 07:44:35 +0900
Michael Paquier <mic...@gm...> wrote:

> On Tue, Jul 24, 2012 at 7:37 AM, Joshua D. Drake <jd...@co...>wrote:
> 
> >
> > On 07/23/2012 03:34 PM, Michael Paquier wrote:
> >
> >      Agreed, which is why I suggested keeping our hands clean but forcing
> >> the
> >>     good community-citizen approach with attribution.
> >>
> >> On this point I kind of agree, everything that is labelled as
> >> "Postgres-XC development group" should be based on the same license as
> >> the code to facilitate all the things.
> >> However, docs written by guys not using Postgres-XC development group
> >> name on their docs but a personal name or company name can provide the
> >> license they want and if other people want to pick up those documents
> >> they need to contact the authors. This is for example the case of my own
> >> presentation documents. Those docs are under non-commercial as I use on
> >> them my company name and my own name.
> >>
> >
> > There is no way to force any author to release any document under any
> > license except in the instance where the author would like to contribute
> > that documentation directly to the Postgres-XC development group. In that
> > case (say a patch submission, or acceptance on the website or wiki) we can
> > force a specific license. Otherwise, we are powerless.
> 
> So we agree here.
> 
> 
> >  So Michael, I believe with that your concerns are addressed, yes?
> 
> Yes.
> -- 
> Michael Paquier
> http://michael.otacoo.com

On Tue, Jul 24, 2012 at 7:37 AM, Joshua D. Drake <jd...@co...>wrote:

>
> On 07/23/2012 03:34 PM, Michael Paquier wrote:
>
>      Agreed, which is why I suggested keeping our hands clean but forcing
>> the
>>     good community-citizen approach with attribution.
>>
>> On this point I kind of agree, everything that is labelled as
>> "Postgres-XC development group" should be based on the same license as
>> the code to facilitate all the things.
>> However, docs written by guys not using Postgres-XC development group
>> name on their docs but a personal name or company name can provide the
>> license they want and if other people want to pick up those documents
>> they need to contact the authors. This is for example the case of my own
>> presentation documents. Those docs are under non-commercial as I use on
>> them my company name and my own name.
>>
>
> There is no way to force any author to release any document under any
> license except in the instance where the author would like to contribute
> that documentation directly to the Postgres-XC development group. In that
> case (say a patch submission, or acceptance on the website or wiki) we can
> force a specific license. Otherwise, we are powerless.

So we agree here.


>  So Michael, I believe with that your concerns are addressed, yes?

Yes.
-- 
Michael Paquier
http://michael.otacoo.com

On 07/23/2012 03:34 PM, Michael Paquier wrote:

>     Agreed, which is why I suggested keeping our hands clean but forcing the
>     good community-citizen approach with attribution.
>
> On this point I kind of agree, everything that is labelled as
> "Postgres-XC development group" should be based on the same license as
> the code to facilitate all the things.
> However, docs written by guys not using Postgres-XC development group
> name on their docs but a personal name or company name can provide the
> license they want and if other people want to pick up those documents
> they need to contact the authors. This is for example the case of my own
> presentation documents. Those docs are under non-commercial as I use on
> them my company name and my own name.

There is no way to force any author to release any document under any 
license except in the instance where the author would like to contribute 
that documentation directly to the Postgres-XC development group. In 
that case (say a patch submission, or acceptance on the website or wiki) 
we can force a specific license. Otherwise, we are powerless.

So Michae, I believe with that your concerns are addressed, yes?

Sincerely,

Joshua D. Drake


> --
> Michael Paquier
> http://michael.otacoo.com


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

On Tue, Jul 24, 2012 at 1:36 AM, Joshua D. Drake <jd...@co...>wrote:

>
> On 07/21/2012 01:01 PM, Mason Sharp wrote:
> >
> > On Fri, Jul 20, 2012 at 10:00 PM, Koichi Suzuki
> > <koi...@gm...> wrote:
> >> As Mason suggested, I think it's safer to begin with non-commercial
> >> license.   Commercial use can be licensed in case-by-case basis and we
> >> should license as long as the use helps XC.   There could be many
> >> different commercial use and I'm not sure if the commercial license
> >> helps XC in many corner cases.
> >>
> >
> > Actually, I just meant that I think anything created by the
> > "Postgres-XC Development Group" as a whole should allow liberal usage
> > (whatever license that would be), including commercial use, and that
> > if someone creates something and wants some restrictions, they should
> > do it under their own name or company. Isn't that similar to the
> > PostgreSQL community?
>
> Well PostgreSQL is 100% BSD (docs included) so.... you can pretty much
> do whatever you want.
>
> >  If the others in the XC community wants to go a
> > different route, that's fine, I just hope it does not become overly
> > bureaucratic.
>
> Agreed, which is why I suggested keeping our hands clean but forcing the
> good community-citizen approach with attribution.
>
On this point I kind of agree, everything that is labelled as "Postgres-XC
development group" should be based on the same license as the code to
facilitate all the things.
However, docs written by guys not using Postgres-XC development group name
on their docs but a personal name or company name can provide the license
they want and if other people want to pick up those documents they need to
contact the authors. This is for example the case of my own presentation
documents. Those docs are under non-commercial as I use on them my company
name and my own name.
-- 
Michael Paquier
http://michael.otacoo.com

On 07/21/2012 01:01 PM, Mason Sharp wrote:
>
> On Fri, Jul 20, 2012 at 10:00 PM, Koichi Suzuki
> <koi...@gm...> wrote:
>> As Mason suggested, I think it's safer to begin with non-commercial
>> license.   Commercial use can be licensed in case-by-case basis and we
>> should license as long as the use helps XC.   There could be many
>> different commercial use and I'm not sure if the commercial license
>> helps XC in many corner cases.
>>
>
> Actually, I just meant that I think anything created by the
> "Postgres-XC Development Group" as a whole should allow liberal usage
> (whatever license that would be), including commercial use, and that
> if someone creates something and wants some restrictions, they should
> do it under their own name or company. Isn't that similar to the
> PostgreSQL community?

Well PostgreSQL is 100% BSD (docs included) so.... you can pretty much 
do whatever you want.

>  If the others in the XC community wants to go a
> different route, that's fine, I just hope it does not become overly
> bureaucratic.

Agreed, which is why I suggested keeping our hands clean but forcing the 
good community-citizen approach with attribution.

Sincerely,

Joshua D. Drake


>
> --
> Mason Sharp
>
> StormDB - http://www.stormdb.com
> The Database Cloud
>


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

Sorry, it was a wrong refer.   Joshua suggested some of the
fundraising and copyright.   Anyway, I think it's better to start with
non-commercial and see what corner cases we should be careful about.

Regards;
----------
Koichi Suzuki


2012/7/22 Mason Sharp <ma...@st...>:
> On Fri, Jul 20, 2012 at 10:00 PM, Koichi Suzuki
> <koi...@gm...> wrote:
>> As Mason suggested, I think it's safer to begin with non-commercial
>> license.   Commercial use can be licensed in case-by-case basis and we
>> should license as long as the use helps XC.   There could be many
>> different commercial use and I'm not sure if the commercial license
>> helps XC in many corner cases.
>>
>
> Actually, I just meant that I think anything created by the
> "Postgres-XC Development Group" as a whole should allow liberal usage
> (whatever license that would be), including commercial use, and that
> if someone creates something and wants some restrictions, they should
> do it under their own name or company. Isn't that similar to the
> PostgreSQL community?  If the others in the XC community wants to go a
> different route, that's fine, I just hope it does not become overly
> bureaucratic.
>
> --
> Mason Sharp
>
> StormDB - http://www.stormdb.com
> The Database Cloud

On Fri, Jul 20, 2012 at 10:00 PM, Koichi Suzuki
<koi...@gm...> wrote:
> As Mason suggested, I think it's safer to begin with non-commercial
> license.   Commercial use can be licensed in case-by-case basis and we
> should license as long as the use helps XC.   There could be many
> different commercial use and I'm not sure if the commercial license
> helps XC in many corner cases.
>

Actually, I just meant that I think anything created by the
"Postgres-XC Development Group" as a whole should allow liberal usage
(whatever license that would be), including commercial use, and that
if someone creates something and wants some restrictions, they should
do it under their own name or company. Isn't that similar to the
PostgreSQL community?  If the others in the XC community wants to go a
different route, that's fine, I just hope it does not become overly
bureaucratic.

--
Mason Sharp

StormDB - http://www.stormdb.com
The Database Cloud

Found this.   The article refers to XC as well.
----------
Koichi Suzuki



---------- Forwarded message ----------
From: Chris Travers <chr...@gm...>
Date: 2012/7/20
Subject: [pgsql-advocacy] PostgreSQL Rising on Hackers News
To: pgsql-advocacy <pgs...@po...>


http://news.ycombinator.com/item?id=4268525

Thought folks here might find it interesting.

Best Wishes,
Chris Travers

As Mason suggested, I think it's safer to begin with non-commercial
license.   Commercial use can be licensed in case-by-case basis and we
should license as long as the use helps XC.   There could be many
different commercial use and I'm not sure if the commercial license
helps XC in many corner cases.

Regards;
----------
Koichi Suzuki


2012/7/20 Joshua D. Drake <jd...@co...>:
>
> Hello,
>
> Alright just so this topic doesn't die, this is my recommendation. I
> believe that the documentation and any "Official" community
> documentation should be licensed under:
>
> http://creativecommons.org/licenses/by-sa/3.0/
>
> This allows commercial use but enforces good commercial participation in
> the community by requiring that modifications must be given back under
> the same license. In this way, changes we want as part of the community
> we can push back into the official docs at will.
>
> Sincerely,
>
> Joshua D. Drake
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

On 07/19/2012 10:10 PM, Michael Paquier wrote:
> Thanks for spending time on that. The structure looks nice and
> sufficient for its purpose.
>
> I am just wondering about a couple of things...
> 1) in the documentation part, why only having a link refering to the
> docs in SourceForge? Wouldn't it make more sense to generate the docs
> automatically at each minor or major release?

Yes I just don't have that setup.

> It would also be extremely
> nice for all the developers and users to have an automatic build of
> latest development docs on master branch. Referring only to the
> sourceforge site is not really a big matter in itself but makes your
> sire structure dependent on what is in sourceforge.

Yeah I don't see that as a problem.

> 2) SourceForge is stopping support of MediaWiki at the beginning of
> September, you should remove the link to it.

Are we going to grab the content?

> 3) I also maintain a repository in Github:
> https://github.com/postgres-xc/postgres-xc. This is just a mirror but it
> is far more readable than the ugly sourceforge interface. It might be
> worth referring to it.

I would think that the GitHub should be the master branch :)

jD

>
>
> --
> Michael Paquier
> http://michael.otacoo.com


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

On Fri, Jul 20, 2012 at 5:32 PM, Vladimir Stavrinov <vst...@gm...>wrote:

> I have fresh installed XC consisting of two data nodes with all defaults
> settings. Nothing special was configured. I have created database and
> one table with one only text field. Then I inserted text string and
> tried SELECT. At this point all was OK. But after shutting down of one
> data node SELECT fails returning the message in subject. This is
> not what was I expected. DROP DATANODE doesn't help. If it is not a bug,
> then I have questions:
>
This is not a bug. What you did here was removed a component from the
cluster.
An incomplete cluster will not work.


>
> 1. What should failover and then recovery procedures be after one
> data node fails?
>
Like postgreSQL, you can attach a slave node to a datanode and then perform
a failover on it.
After the master node fails for a reason or another, you will need to
promote a slave waiting behind.
Something like pg_ctl promote -D $DN_FOLDER is enough.
This is for the Datanode side.
Then what you need to do is update the node catalogs on each Coordinator to
allow them to redirect to the new promoted node.
Let's suppose that the node that failed was called datanodeN (you need the
same node name for master and slave).
In order to do that, issue "ALTER NODE datanodeN WITH (HOST = '$new_ip',
PORT = $NEW_PORT); SELECT pgxc_pool_reload();"
Do that on each Coordinator and then the promoted slave will be visible to
each Coordinator and will be a part of cluster.


> 2. Does this means, that XC is scalable in one only direction, that is
> it can be expanded, but not shrunk? In other words, we cannot remove
> data node.
>
You can remove a Datanode, just be sure that before doing that you redirect
to an existing node the data of distributed tables.
In 1.0 you can do that with those kind of things (want to remove data from
datanodeN):
CREATE TABLE new_table TO NODE (datanode1, ... datanode(N-1),
datanode(N+1), datanodeP) AS SELECT * from old_table;
DROP TABLE old_table;
ALTER TABLE new_table RENAME TO old_table;
Once you are sure that the datanode you want to remove has no unique data
(don't care about replicated...), perform a DROP NODE on each Coordinator,
then pgxc_pool_reload() and the node will be removed correctly.
Please note that I working on a patch able to do such stuff
automatically... Will be committed soon.

>
> 3. Does this means, that without external infrastructure (like drbd +
> corosync + pacemaker)  with default setup (CREATE TABLE ...
> DISTRIBUTE BY REPLICATION) XC itself have no neither HA nor LB (at least
> for writes) capabilities?
>
Basically it has both, I know some guys who are already building an HA/LB
solution based on that...
-- 
Michael Paquier
http://michael.otacoo.com

I have fresh installed XC consisting of two data nodes with all defaults
settings. Nothing special was configured. I have created database and
one table with one only text field. Then I inserted text string and
tried SELECT. At this point all was OK. But after shutting down of one 
data node SELECT fails returning the message in subject. This is 
not what was I expected. DROP DATANODE doesn't help. If it is not a bug,
then I have questions:

1. What should failover and then recovery procedures be after one
data node fails?

2. Does this means, that XC is scalable in one only direction, that is
it can be expanded, but not shrunk? In other words, we cannot remove
data node.

3. Does this means, that without external infrastructure (like drbd +
corosync + pacemaker)  with default setup (CREATE TABLE ...
DISTRIBUTE BY REPLICATION) XC itself have no neither HA nor LB (at least
for writes) capabilities?

If all this true, it is not a cluster that I imagined after reading
XC description and what is expected from cluster at all.

-- 

***************************
##  Vladimir Stavrinov
##  vst...@gm...
***************************

Thanks for spending time on that. The structure looks nice and sufficient
for its purpose.

I am just wondering about a couple of things...
1) in the documentation part, why only having a link refering to the docs
in SourceForge? Wouldn't it make more sense to generate the docs
automatically at each minor or major release? It would also be extremely
nice for all the developers and users to have an automatic build of latest
development docs on master branch. Referring only to the sourceforge site
is not really a big matter in itself but makes your sire structure
dependent on what is in sourceforge.
2) SourceForge is stopping support of MediaWiki at the beginning of
September, you should remove the link to it.
3) I also maintain a repository in Github:
https://github.com/postgres-xc/postgres-xc. This is just a mirror but it is
far more readable than the ugly sourceforge interface. It might be worth
referring to it.

I am sure there will be other comments from members.
BR & thx!

On Fri, Jul 20, 2012 at 8:24 AM, Joshua D. Drake <jd...@co...>wrote:

>
> Hello,
>
> I know it has been a few weeks but we spend some time on the proposed
> new site. Not a whole lot of time but enough to actually have a
> structure. Please take a look at provide feedback:
>
> http://xc.commandprompt.com/
>
> JD
> --
> Command Prompt, Inc. - http://www.commandprompt.com/
> PostgreSQL Support, Training, Professional Services and Development
> High Availability, Oracle Conversion, Postgres-XC
> @cmdpromptinc - 509-416-6579
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>



-- 
Michael Paquier
http://michael.otacoo.com

Hello,

I know it has been a few weeks but we spend some time on the proposed 
new site. Not a whole lot of time but enough to actually have a 
structure. Please take a look at provide feedback:

http://xc.commandprompt.com/

JD
-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579

Hello,

Alright just so this topic doesn't die, this is my recommendation. I 
believe that the documentation and any "Official" community 
documentation should be licensed under:

http://creativecommons.org/licenses/by-sa/3.0/

This allows commercial use but enforces good commercial participation in 
the community by requiring that modifications must be given back under 
the same license. In this way, changes we want as part of the community 
we can push back into the official docs at will.

Sincerely,

Joshua D. Drake

On Sat, Jul 14, 2012 at 2:06 PM, Aris Setyawan <ari...@gm...> wrote:

> Hi,
>
> I was able to configure postgresql 9.1 for total memory usage about
> less than(in lowend VPS)  8MB.
>
That's kind of low... Do you know that shared_buffers is usually set at 25%
of your machine shared memory in average for PostgreSQL?


>
> How about postgres-xc data-node behavior? Is it still the same way with
> ordinary postgresql to configure?
>
Yes, it should be the same.
The only differences are:
1) XC uses 2PC internally when a transaction involves more than 2 nodes in
a write operation. So be sure to set up max_prepared_xacts to a good value.
2) Set max_connections on Datanodes in accordance with your coordinators.
Each Datanode may receive a connection from each Coordinator backend. For
example, if you have a cluster with 20 Coordinators having the same
max_connections value set. The absolute maximum of connections that 1
Datanode of your cluster can get is 20 * max_connections. You should never
reach this absolute value in practice, but just be aware of that depending
on your application.



> How about GTM memory usage? Can I limit their memory?
>
There are no GUC parameters that allow in gtm.conf that allow to control
the memory used at GTM level.
You can still change the maximum number of backends allowed in GTM. This
could bring some kind of control on the max memory a GTM uses.
-- 
Michael Paquier
http://michael.otacoo.com

The Postgres-XC documentation and articles/talks/presentation etc.
material, based on XC are two different matters.

For Postgres-XC documentation, the license similar to code should apply. I
don't think there is

For rest of the material/media produced, I don't think, we can enforce any
kind of copy-right as such. The copy-right/licensing will solely depend
upon the author OR the sponsor for such work OR the media where the
material gets published. In fact, we may not be able to enforce any rules
on such production.

If any individual on his/her own is producing a piece of information about
XC, its experience etc. s/he will decide how this material can be further
used and will be governed by the material s/he uses to produce this
material. If the work is being sponsored by someone, the sponsor would be
deciding the terms of usage of such material. In many cases, where such
material is published in magazines or conferences or proceedings, the
publishers have their own copy-right/license rules.

We still can decide what rules to apply to the material produced till date,
which is out of any copy-right/licensing terms.

On Thu, Jul 12, 2012 at 11:10 AM, Michael Paquier <mic...@gm...
> wrote:

>
>
> On Thu, Jul 12, 2012 at 2:34 PM, Koichi Suzuki <koi...@gm...>wrote:
>
>> As raised by Mason and commented by many members, I think it's a time
>> to determine how XC-related documents/contents license should be.
>> Here's my idea.
>>
>> 1. As Mason proposed, I think creative commons is suitable for XC
>> documents/contents (except for the code and the reference, they're
>> licensed under PostgreSQL license).
>> 2. Only for non-commercial use.   For commercial use, need specific
>> approval.
>> 3.  Share-alike.  Can distribute the resulting work only under the
>> same or similar license.
>>
> OK here.
>
>> 4. Original Author.   I'm thinking at least "Postgres-XC development
>> group" should be referred as an original author in derived work.
>>
> As suggested by Pavan and you, XC Development group will be enough... This
> is going to be a pain through years if we look for a special author on a
> special document.
>
>




>
>> If anybody would like to use XC documents/contents commercially, they
>> need to have specific approval.
>
> Or they can make a new one from scratch.
>
>>   I'm also thinking to establish "fund
>> raising group" who receives and approves commercial use, as well as
>> future fundraising work.   This is closed group consists of selected
>> XC mailing list reader.   I'd like to draft update to the charter of
>> the group for comments.
>>
> Those are good ideas, able to diversify the origin of funds able to reach
> the project.
> --
> Michael Paquier
> http://michael.otacoo.com
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Enterprise Postgres Company

No, we don't have a menas to limit GTM memory usage.   Most of the
memory is for temporary basis.    Only memory with long lifetime is
the structure to hold current live transactions.   It is very very
small compared with those datanode/coordinator consumes so I thought
usual GTM installation will never be suffered for the memory shortage.

Regards;
----------
Koichi Suzuki


2012/7/14 Aris Setyawan <ari...@gm...>:
> Hi,
>
> I was able to configure postgresql 9.1 for total memory usage about
> less than(in lowend VPS)  8MB.
>
> How about postgre-xc data-node behavior? Is it still the same way with
> ordinary postgresql to configure?
>
> How about GTM memory usage? Can I limit their memory?
>
> -thanks
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general

"Commercial" has very very wide corner cases and I think it's  not
practical to allow "any" commercial use.   Reference document, as you
find in doc-xc in our GIT is licensed under PostgreSQL license and is
exceptional because it is essentially the same as the code.

For other materials, they have different backgrounds and is reasonable
to allow only non-commercial user while the users can change the
contents.    As suggested, individual document can be given different
copyright or license as done in PG materials.

I also think that commercial use should be licensed individually and
should be licensed free or almost free if the use helps XC community.

Yes, fundraising group will help for the licensing, as well as more
general financial help.   Getting financial help from organizations
other than NTT is very very helpful for XC community.     It will be
nice to begin to discuss this.

Regards;
----------
Koichi Suzuki


2012/7/14 Michael Paquier <mic...@gm...>:
>
>
> On Fri, Jul 13, 2012 at 10:27 PM, Mason Sharp <ma...@st...> wrote:
>>
>> On Thu, Jul 12, 2012 at 8:21 PM, Koichi Suzuki <ko...@in...>
>> wrote:
>> > Mason is proposing that it's better to license XC contents commercially
>> > as well.
>> >
>>
>> I am just saying that anything from the Postgres-XC Development Group
>> could be like the PostgreSQL Development Group and allow liberal
>> usage. If someone does not want to allow liberal usage, then they put
>> it under their own name or company name instead of the Postgres-XC
>> Development Group, and under any such license that they choose (is
>> that more similar to how PostgreSQL also operates?).  It seems like an
>> easy way to avoid disagreements and avoid adding bylaws, committees
>> and bureaucracy.
>
> Just to be clear: what are the documents you are talking about?
> If it is the documentation in GIT, then it falls under Postgres-XC
> Development Group copyright and is licensed as PostgreSQL license.
> If it is the presentation documents that have been used at conferences, this
> is different. And in this case if you want to reuse those materials you
> might need to contact the authors except if they decided to transmit the
> copyright of their documents under Postgres-XC Development Group. For
> example, I haven't written any presentation document under Postgres-XC
> Development group label, and I don't recall that I transmitted the right to
> use my own presentation slides for commercial usages.
> --
> Michael Paquier
> http://michael.otacoo.com
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>

Hi,

I was able to configure postgresql 9.1 for total memory usage about
less than(in lowend VPS)  8MB.

How about postgre-xc data-node behavior? Is it still the same way with
ordinary postgresql to configure?

How about GTM memory usage? Can I limit their memory?

-thanks