postgres-xc-general Mailing List for Postgres-XC

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
>