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

Hi,

I found an article while browsing the web comparing pgpool-ii, XC and
postgres. OK, that's mostly pgpool but the latest paragraph is what caught
my attention.
It would be nice to get in touch with this guy, it doesn't look that he
heard about the latest news of the project: release of 1.0.
http://www.varnernet.com/~bryan/2012/05/29/i-love-postgresql-but-pgpool-ii-is-another-story/

At least the comment on pgpool-ii is kind of... interesting.
I let see it yourself.

Someone knows who this guy is?
-- 
Michael Paquier
http://michael.otacoo.com

On Sat, Jun 9, 2012 at 10:29 AM, Michael Vitale <mic...@ar...> wrote:

> Thanks for the responses.  I'd like to pursue the jdbc driver issue for
> Postgres-xc a bit more...
>
> Regarding the jdbc driver for Postgresql, it would be neat if we could
> take a current cut of the postgresql jdbc driver and customize it for
> postgres-xc, so that the input connection string could contain an array of
> coordinator addresses, just like oracleRAC, so we could have "automatic
> failover" at the coordinator node level embedded right into the jdbc
> driver.  Consider new jdbc pseudo code:
>

I think jdbc driver has already some failover functionalities already
included in it, but honestly not sure.
So it might be that there is already some code in that would help to
support multiple connections to cluster nodes.
However I am not really updated on the development so perhaps such a
feature is not implemented, but I am sure that JDBC guys might be
interested in such a feature to redirect read-only queries to slave nodes
for example just for vanilla postgres.

Btw, the functionality you propose would be helpful for both projects.
You should have a look here to get in touch with the latest development:
http://github.com/pgjdbc/pgjdbc.


>
> If sql connect error encountered, see if the connection string contains
> another coordinator address and if so, connect to that coordinator and set
> its handle globally to replace the original connection handle so other
> threads will use it as well for future IO requests to the database.
>
> Now of course this doesn't handle failover at the data node level, but is
> seems like it would sure do the trick at the coordinator node level.
>
Yes that would be helpful. But be sure to check if there is not already
some infrastructure in jdbc itself.

Even if automatic failover on Datanodes is a core feature, there are
already some ways to check if a Datanode is alive or not from a
Coordinator, so you could also know when a Datanode is down and promote a
slave attached to it.
There is a functionality called EXECUTE DIRECT whose doc is here:
http://postgres-xc.sourceforge.net/docs/1_0/sql-executedirect.html
This SQL specific to XC allows to launch a query directly to a remote node,
Coordinator or Datanode when connected on a Coordinator.

For example, let's imagine that your driver is connected to Coordinator
called node_coord1, and you have Datanodes called node_dn1, node_dn2, ...
node_dnN.
You can simply check if the node (here node_dn2) is alive by launching
something like:
EXECUTE DIRECT ON NODE node_dn2 'SELECT 1';
If the node is offline for a reason or another pooler will complain telling
that it cannot get a connection to remote node.

You can also use that from a Coordinator to check if a remote Coordinator
is down.


>
> Now let me compare this new postgres-xc jdbc driver to HA failover already
> embedded in JBOSS AS 7.  It would be much better, because while JBOSS would
> allow you to input multiple jdbc connection strings (using the vertical bar
> separator), it does not break down bad connections and automatically
> reconnect those clients to the other one.  Instead it will just make sure
> that future connection handle requests are directed to the other one.
>  Already connected users would have to manually logoff from their
> applications and log on again.  But if we embed multiple coordinators into
> a new Postgres-xc jdbc driver, then the driver will break down the bad
> connections and automatically connect those users to the other cordinators
> without the users having to do anything!
>
> Although I'm calling this a new jdbc driver for postgres-xc, the concept
> would work the same for postgresql and postgres-xc: jdbc driver allows
> specification of multiple database connection parameters.
>
> What you all think?  And if you all know where this would be useful to a
> postgresql jdbc community email address, please forward this.
>
So it would be nice.
Your module should be pluggable on top of jdbc, or even directly included
in jdbc if you consider the case of normal postgreSQL with master and slave
nodes (slave nodes are read-only) for read-query balancing.
-- 
Michael Paquier
http://michael.otacoo.com

We have discussed this issue inside some of the core members.   Your
proposal looks very nice to XC.    I'm interested in how this can be
maintained in a long run.    Do you have any idea?

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


2012/6/9 Michael Vitale <mic...@ar...>:
> Thanks for the responses.  I'd like to pursue the jdbc driver issue for Postgres-xc a bit more...
>
> Regarding the jdbc driver for Postgresql, it would be neat if we could take a current cut of the postgresql jdbc driver and customize it for postgres-xc, so that the input connection string could contain an array of coordinator addresses, just like oracleRAC, so we could have "automatic failover" at the coordinator node level embedded right into the jdbc driver.  Consider new jdbc pseudo code:
>
> If sql connect error encountered, see if the connection string contains another coordinator address and if so, connect to that coordinator and set its handle globally to replace the original connection handle so other threads will use it as well for future IO requests to the database.
>
> Now of course this doesnt handle failover at the data node level, but is seems like it would sure do the trick at the coordinator node level.
>
> Now let me compare this new postgres-xc jdbc driver to HA failover already embedded in JBOSS AS 7.  It would be much better, because while JBOSS would allow you to input multiple jdbc connection strings (using the vertical bar separator), it does not break down bad connections and automatically reconnect those clients to the other one.  Instead it will just make sure that future connection handle requests are directed to the other one.  Already connected users would have to manually logoff from their applications and log on again.  But if we embed multiple coordinators into a new Postgres-xc jdbc driver, then the driver will break down the bad connections and automatically connect those users to the other cordinators without the users having to do anything!
>
> Although I'm calling this a new jdbc driver for postgres-xc, the concept would work the same for postgresql and postgres-xc: jdbc driver allows specification of multiple database connection parameters.
>
> What you all think?  And if you all know where this would be useful to a postgresql jdbc community email address, please forward this.
>
> Respectfully Yours,
> Michael Vitale
>
> ________________________________________
> From: Michael Paquier [mic...@gm...]
> Sent: Friday, June 08, 2012 8:30 AM
> To: Michael Vitale
> Cc: Postgres-XC mailing list
> Subject: Re: [Postgres-xc-general] An article about XC at PgCon
>
> On 2012/06/08, at 20:19, Michael Vitale <mic...@ar...> wrote:
>
>> How do you undo an initdb?  In the case where I want to redefine the initdb differently.  Also, I did the gmake uninstall, but it didn't remove any binary installed files.
> Let's take the problems one-by-one.
> For initdb, you need to delete the data folder and then recreate it. I don't think Postgres can redefine a data folder with initdb and just returns an error telling that existing data folder is not empty.
> gmaje uninstall should work. At least in the environments used here it does.
>>
>> Also, does postgres-xc work well as a High Availability solution, i.e., automatic failover?
> You will need to plug in yourself slave nodes to your master nodes and having  a monitoring engine that performs failover. You got the same problems with Postgres. Its core features cannot perform a failover themselves and you always need to kick something to perform a failover in case of a node failure.
>>
>> I come from an oracle RAC world, and I am playing with postgres-xc 1.0.0 on 2 centos 6, 64 bit boxes.
>>
>> Oracle has failover embedded in its listener configuration and in its jdbc driver.  For instance, the oracle jdbc driver for our jboss server is something like this:
>>
>> <connection-url>jdbc:oracle:thin:@(description=(address_list=(load_balance=on)(failover=off)(address=(protocol=tcp)(host=odb0-vip.arin.net)(port=1521))(address=(protocol=tcp)(host=odb1-vip.arin.net)(port=1521)))(connect_data=(service_name=pjpn.arin.net)(failover_mode=(type=select)(method=basic))))</connection-url>
>>
>> Note that 2 oracle nodes are specified right within the oracle jdbc driver.  For normal PostgreSQL, the driver would look something like this:
>> <connection-url>jdbc:postgresql://dbproto1.arin.net:5432/pjpn</connection-url>
>>
>> So, I'm wondering if there is already a way to specify more than one cordinator in the jdbc connection string for connecting to postgres-xc?
> I am not a specialist of jdbc, but I don't think you can specify multiple connection points in.
>>
>> If not, then I reckon its up to me to implement a vip switched node that would automatically point to another cordinator if the first vip went down.
> Yep think so. The core features of xc should be sufficient for a correct failover.
>>
>> Comments, suggestions?
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
> ------------------------------------------------------------------------------
> 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

Thanks for the responses.  I'd like to pursue the jdbc driver issue for Postgres-xc a bit more...

Regarding the jdbc driver for Postgresql, it would be neat if we could take a current cut of the postgresql jdbc driver and customize it for postgres-xc, so that the input connection string could contain an array of coordinator addresses, just like oracleRAC, so we could have "automatic failover" at the coordinator node level embedded right into the jdbc driver.  Consider new jdbc pseudo code:

If sql connect error encountered, see if the connection string contains another coordinator address and if so, connect to that coordinator and set its handle globally to replace the original connection handle so other threads will use it as well for future IO requests to the database.

Now of course this doesnt handle failover at the data node level, but is seems like it would sure do the trick at the coordinator node level.

Now let me compare this new postgres-xc jdbc driver to HA failover already embedded in JBOSS AS 7.  It would be much better, because while JBOSS would allow you to input multiple jdbc connection strings (using the vertical bar separator), it does not break down bad connections and automatically reconnect those clients to the other one.  Instead it will just make sure that future connection handle requests are directed to the other one.  Already connected users would have to manually logoff from their applications and log on again.  But if we embed multiple coordinators into a new Postgres-xc jdbc driver, then the driver will break down the bad connections and automatically connect those users to the other cordinators without the users having to do anything!

Although I'm calling this a new jdbc driver for postgres-xc, the concept would work the same for postgresql and postgres-xc: jdbc driver allows specification of multiple database connection parameters.

What you all think?  And if you all know where this would be useful to a postgresql jdbc community email address, please forward this.

Respectfully Yours,
Michael Vitale

________________________________________
From: Michael Paquier [mic...@gm...]
Sent: Friday, June 08, 2012 8:30 AM
To: Michael Vitale
Cc: Postgres-XC mailing list
Subject: Re: [Postgres-xc-general] An article about XC at PgCon

On 2012/06/08, at 20:19, Michael Vitale <mic...@ar...> wrote:

> How do you undo an initdb?  In the case where I want to redefine the initdb differently.  Also, I did the gmake uninstall, but it didn't remove any binary installed files.
Let's take the problems one-by-one.
For initdb, you need to delete the data folder and then recreate it. I don't think Postgres can redefine a data folder with initdb and just returns an error telling that existing data folder is not empty.
gmaje uninstall should work. At least in the environments used here it does.
>
> Also, does postgres-xc work well as a High Availability solution, i.e., automatic failover?
You will need to plug in yourself slave nodes to your master nodes and having  a monitoring engine that performs failover. You got the same problems with Postgres. Its core features cannot perform a failover themselves and you always need to kick something to perform a failover in case of a node failure.
>
> I come from an oracle RAC world, and I am playing with postgres-xc 1.0.0 on 2 centos 6, 64 bit boxes.
>
> Oracle has failover embedded in its listener configuration and in its jdbc driver.  For instance, the oracle jdbc driver for our jboss server is something like this:
>
> <connection-url>jdbc:oracle:thin:@(description=(address_list=(load_balance=on)(failover=off)(address=(protocol=tcp)(host=odb0-vip.arin.net)(port=1521))(address=(protocol=tcp)(host=odb1-vip.arin.net)(port=1521)))(connect_data=(service_name=pjpn.arin.net)(failover_mode=(type=select)(method=basic))))</connection-url>
>
> Note that 2 oracle nodes are specified right within the oracle jdbc driver.  For normal PostgreSQL, the driver would look something like this:
> <connection-url>jdbc:postgresql://dbproto1.arin.net:5432/pjpn</connection-url>
>
> So, I'm wondering if there is already a way to specify more than one cordinator in the jdbc connection string for connecting to postgres-xc?
I am not a specialist of jdbc, but I don't think you can specify multiple connection points in.
>
> If not, then I reckon its up to me to implement a vip switched node that would automatically point to another cordinator if the first vip went down.
Yep think so. The core features of xc should be sufficient for a correct failover.
>
> Comments, suggestions?
>
>
> ------------------------------------------------------------------------------
> 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,

You should avoid sending responses to Postgres announce mailing lists people are going to complain. Better to use the MLs dedicated to xc.
Please find my answers below.

On 2012/06/09, at 1:54, Fernando Lozano <fer...@lo...> wrote:

> Hi Michael,
> 
> Very interesting, but the docs states that it is "transparent" only for libpq clients. This means Java clients (using the type 4 JDBC driver) can't use PostgreSQL XC?
Documentation is wrong. We tested with many drivers like php, ruby, perl, jdbc, ecpg, etc.
And the only problems we saw was with odbc because it uses returning and ctid. The rest was working well.
Could you indicate in which page the error is located?
> 
> Also, as far as I understand the docs, I need something external do implement failover if I connect to a database server which comes offline (JBoss AS HA Datasources comes to mind), and there's no balancer included. Am I right?
Yes you are right. There is a kind of load balancing between Datanodes and Coordinators by design thanks to the distributed nature of tables and the possibility to control read for replicated tables on specific nodes. However it might be preferable to have load balancing from something external.

Regards,

Michael
> 
> 
> []s, Fernando Lozano
> 
>> Hi all,
>> 
>> Postgres-XC, read&write-scalable multi-master symmetric cluster based on PostgreSQL, version 1.0.0 is released.
>> This project is seen as an open-source alternative to costly products such as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can naturally use all its technologies, which are enhaunced to have a shared-nothing multi-master PostgreSQL-based database cluster.
>> 
>> This first stable version is based on PostgreSQL 9.1.4. All the patches in PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of June 2012).
>> This includes the security fix related to pg_crypto dated of 30th of May.
>> You can download the source tarball directly from here:
>> https://sourceforge.net/projects/postgres-xc/files/latest/download
>> This tarball contains all the HTML and man documentation.
>> 
>> 30 bug fixes have been made since release of beta2, with some notable enhancements:
>> - Support for EXTENSION is fixed
>> - Stabilization of the use of slave nodes in cluster
>> - Fix of a bug related to read-only transactions, improving performance by 15%.
>> - Support of compilation for MacOSX
>> About the scalability of this release, Postgres-XC 1.0.0 scales to a factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 nodes using a benchmark called DBT-1.
>> 
>> Compared to version Postgres-XC 0.9.7, the following features have been added:
>> - Fast query shipping (FQS), quick identification of expressions in a query that can be pushed down to remote nodes
>> - SERIAL types
>> - TABLESPACE
>> - Utility to clean up 2PC transactions in cluster (pgxc_clean)
>> - Utility for initialization of GTM (global transaction manager, utility called initgtm)
>> - Relation-size functions and locking functions
>> - Regression stabilization
>> 
>> The documentation of 1.0, including release notes, is available here:
>> http://postgres-xc.sourceforge.net/docs/1_0/.
>> 
>> The project can be followed on Source Forge: http://postgres-xc.sourceforge.net/.
>> And a couple of GIT repositories are used for development:
>> - SourceForge: http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
>> - Github: https://github.com/postgres-xc/postgres-xc
>> 
>> The core team is currently working in the addition of new features for the next major release including:
>> - Merge with PostgreSQL 9.2
>> - Data redistribution functionality, changing table distribution in cluster with a simple ALTER TABLE
>> - New functionalities related to online node addition and deletion for a better user experience
>> - Triggers
>> - Planner improvements
>> - Global constraints.
>> The roadmap of the project is located here => http://postgres-xc.sourceforge.net/ in section Roadmap.
>> 
>> The project is under the same license as PostgreSQL, now managed under a single entity called "Postgres-XC Development Group".
>> In order to keep in touch with the project, whose development follows the same model as PostgreSQL, you can register to the following mailing lists:
>> - pos...@li..., for general questions. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> - pos...@li.... hachers mailing list. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>> 
>> See you soon on the project mailing list, and have fun with this stable release.
>> -- 
>> Michael Paquier
>> Member of core team of Postgres-XC, and Postgres-XC Development Group
> 
> 

On Fri, Jun 8, 2012 at 1:20 AM, Michael Paquier
<mic...@gm...> wrote:
>
>> I have read the (just) story about bizgres and c-store, from it's
>> development progress until it was commercialized by it's developer.
>> That's so sad because the original project was not to be maintained.
>

I guess that can happen if others apart from the original developers
don't jump in.

> Postgres-XC is under BSD license (PostgreSQL license), so you can edit the
> code, copy the code and even sell it if you wish as a closed source package.
> You can also make money from it by becoming a specialist of this technology
> and sell support and consulting services.
> However there are really few specialists in the world that really understand
> deeply this kind of technology, and even lesser who can work on the code or
> design applications for clusters based on XC.
>
>> What are Postgres-XC plans, will be in the future?

A roadmap appears here:

http://postgres-xc.sourceforge.net/roadmap.html

If you are concerned if development will continue, yes, there are
plans for now.  Even outside of the originally companies involved,
others are going to contribute, too. I no longer work for one of the
original companies behind XC, but I and others intend to contribute to
the project, so I think you can be optimistic about it.

>
> Becoming a reference and a real alternative to closed source (and costly)
> solutions like one I won't give the name (Or????AC).
>
>> How to achieve them?
>
> By supporting and helping the project.
> There are several ways to support the project:
> - first learn how to use it
> - register to the mailing lists and do not hesitate to ask questions
> - report bugs, even better => report bugs and submit patches fixing them.
> - improve the documentation and submit patch for that
> - build and publish packages
> - search for funds to support developers if you want some new features
> - promote the project at conferences or by writing articles about it.
> - provide machines for buildfarming and extend the currently supported OS.
> - provide some website architecture similar to postgresql.org.
> That's all I have in mind now... However, there may be some other things
> people could do.

Good list.

Mason

On 2012/06/08, at 20:19, Michael Vitale <mic...@ar...> wrote:

> How do you undo an initdb?  In the case where I want to redefine the initdb differently.  Also, I did the gmake uninstall, but it didn't remove any binary installed files.
Let's take the problems one-by-one.
For initdb, you need to delete the data folder and then recreate it. I don't think Postgres can redefine a data folder with initdb and just returns an error telling that existing data folder is not empty.
gmaje uninstall should work. At least in the environments used here it does.
> 
> Also, does postgres-xc work well as a High Availability solution, i.e., automatic failover?
You will need to plug in yourself slave nodes to your master nodes and having  a monitoring engine that performs failover. You got the same problems with Postgres. Its core features cannot perform a failover themselves and you always need to kick something to perform a failover in case of a node failure.
> 
> I come from an oracle RAC world, and I am playing with postgres-xc 1.0.0 on 2 centos 6, 64 bit boxes.
> 
> Oracle has failover embedded in its listener configuration and in its jdbc driver.  For instance, the oracle jdbc driver for our jboss server is something like this:
> 
> <connection-url>jdbc:oracle:thin:@(description=(address_list=(load_balance=on)(failover=off)(address=(protocol=tcp)(host=odb0-vip.arin.net)(port=1521))(address=(protocol=tcp)(host=odb1-vip.arin.net)(port=1521)))(connect_data=(service_name=pjpn.arin.net)(failover_mode=(type=select)(method=basic))))</connection-url>
> 
> Note that 2 oracle nodes are specified right within the oracle jdbc driver.  For normal PostgreSQL, the driver would look something like this:
> <connection-url>jdbc:postgresql://dbproto1.arin.net:5432/pjpn</connection-url>
> 
> So, I'm wondering if there is already a way to specify more than one cordinator in the jdbc connection string for connecting to postgres-xc?
I am not a specialist of jdbc, but I don't think you can specify multiple connection points in.
> 
> If not, then I reckon its up to me to implement a vip switched node that would automatically point to another cordinator if the first vip went down.
Yep think so. The core features of xc should be sufficient for a correct failover.
> 
> Comments, suggestions?
> 
> 
> ------------------------------------------------------------------------------
> 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

How do you undo an initdb?  In the case where I want to redefine the initdb differently.  Also, I did the gmake uninstall, but it didn't remove any binary installed files.

Also, does postgres-xc work well as a High Availability solution, i.e., automatic failover?

I come from an oracle RAC world, and I am playing with postgres-xc 1.0.0 on 2 centos 6, 64 bit boxes.

Oracle has failover embedded in its listener configuration and in its jdbc driver.  For instance, the oracle jdbc driver for our jboss server is something like this:

<connection-url>jdbc:oracle:thin:@(description=(address_list=(load_balance=on)(failover=off)(address=(protocol=tcp)(host=odb0-vip.arin.net)(port=1521))(address=(protocol=tcp)(host=odb1-vip.arin.net)(port=1521)))(connect_data=(service_name=pjpn.arin.net)(failover_mode=(type=select)(method=basic))))</connection-url>

Note that 2 oracle nodes are specified right within the oracle jdbc driver.  For normal PostgreSQL, the driver would look something like this:
<connection-url>jdbc:postgresql://dbproto1.arin.net:5432/pjpn</connection-url>

So, I'm wondering if there is already a way to specify more than one cordinator in the jdbc connection string for connecting to postgres-xc?

If not, then I reckon its up to me to implement a vip switched node that would automatically point to another cordinator if the first vip went down.

Comments, suggestions?

Very nice.   The article evaluate XC technology very reasonablly.
---
Koichi

On Fri, 8 Jun 2012 12:36:42 +0900
Michael Paquier <mic...@gm...> wrote:

> Hi all,
> 
> Here is a small article about XC at PGCon:
> http://lwn.net/Articles/498853/
> 
> The project is presented as a clear initiative to OracleRAC.
> -- 
> Michael Paquier
> http://michael.otacoo.com

> I have read the (just) story about bizgres and c-store, from it's
> development progress until it was commercialized by it's developer.
> That's so sad because the original project was not to be maintained.
>
Postgres-XC is under BSD license (PostgreSQL license), so you can edit the
code, copy the code and even sell it if you wish as a closed source package.
You can also make money from it by becoming a specialist of this technology
and sell support and consulting services.
However there are really few specialists in the world that really
understand deeply this kind of technology, and even lesser who can work on
the code or design applications for clusters based on XC.

What are Postgres-XC plans, will be in the future?
>
Becoming a reference and a real alternative to closed source (and costly)
solutions like one I won't give the name (Or????AC).

How to achieve them?
>
By supporting and helping the project.
There are several ways to support the project:
- first learn how to use it
- register to the mailing lists and do not hesitate to ask questions
- report bugs, even better => report bugs and submit patches fixing them.
- improve the documentation and submit patch for that
- build and publish packages
- search for funds to support developers if you want some new features
- promote the project at conferences or by writing articles about it.
- provide machines for buildfarming and extend the currently supported OS.
- provide some website architecture similar to postgresql.org.
That's all I have in mind now... However, there may be some other things
people could do.

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

Thanks Michael for sharing this. It's nice article.

On Fri, Jun 8, 2012 at 9:06 AM, Michael Paquier
<mic...@gm...>wrote:

> Hi all,
>
> Here is a small article about XC at PGCon:
> http://lwn.net/Articles/498853/
>
> The project is presented as a clear initiative to OracleRAC.
> --
> 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

Hi,

I have read the (just) story about bizgres and c-store, from it's
development progress until it was commercialized by it's developer.
That's so sad because the original project was not to be maintained.

What are Postgre-XC plans, will be in the future?
How to achieve them?

On 6/8/12, Michael Paquier <mic...@gm...> wrote:
> Hi all,
>
> Here is a small article about XC at PGCon:
> http://lwn.net/Articles/498853/
>
> The project is presented as a clear initiative to OracleRAC.
> --
> Michael Paquier
> http://michael.otacoo.com
>

Hi all,

Here is a small article about XC at PGCon:
http://lwn.net/Articles/498853/

The project is presented as a clear initiative to OracleRAC.
-- 
Michael Paquier
http://michael.otacoo.com

We should definitely avoid to create threads based on announces done on
PostgreSQL mailing lists...
Sorry for the incovenience.

On Fri, Jun 8, 2012 at 9:02 AM, Michael Paquier
<mic...@gm...>wrote:

>
>
> On Thu, Jun 7, 2012 at 11:06 PM, Michael Vitale <mic...@ar...> wrote:
>
>>  is there an RPM for 1.0.0, and if so, where?
>>
> It looks that Devrim is going to work on that.
> If you are interested in the RPM specs, I uploaded the ones used by Devrim
> for 0.9.4 and 0.9.5 here:
>
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/pgxcrpm;a=summary
>
> Regards,
> --
> Michael Paquier
> http://michael.otacoo.com
>



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

On Thu, Jun 7, 2012 at 11:06 PM, Michael Vitale <mic...@ar...> wrote:

>  is there an RPM for 1.0.0, and if so, where?
>
It looks that Devrim is going to work on that.
If you are interested in the RPM specs, I uploaded the ones used by Devrim
for 0.9.4 and 0.9.5 here:
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/pgxcrpm;a=summary

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

On Thu, 2012-06-07 at 14:06 +0000, Michael Vitale wrote:
> is there an RPM for 1.0.0, and if so, where?

Not yet, but I have a plan to work on this next week.

Regards,
-- 
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

Please just hit *reply* *not* *reply to all*.

Thanks
Saludos
Alfredo Torres
Hab.+58 212 9446304
Cel. +58 412 7109231





2012/6/7 Michael Vitale <mic...@ar...>

>  question regarding the "--with-libxml" configure option during the
> install...
>
> Does this mean that certain XML functions like XMLPARSE will not work
> unless I install with this option?
>
>
>
>
>  ------------------------------
> *From:* Michael Vitale [mic...@ar...]
> *Sent:* Thursday, June 07, 2012 10:06 AM
> *To:* Michael Paquier; Postgres-XC mailing list; PostgreSQL mailing lists
> *Subject:* Re: [Postgres-xc-general] Release of Postgres-XC 1.0.0
>
>   is there an RPM for 1.0.0, and if so, where?
>
>
>  ------------------------------
> *From:* Michael Paquier [mic...@gm...]
> *Sent:* Thursday, June 07, 2012 3:30 AM
> *To:* Postgres-XC mailing list; PostgreSQL mailing lists
> *Subject:* [Postgres-xc-general] Release of Postgres-XC 1.0.0
>
>  Hi all,
>
> Postgres-XC, read&write-scalable multi-master symmetric cluster based on
> PostgreSQL, version 1.0.0 is released.
> This project is seen as an open-source alternative to costly products such
> as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can
> naturally use all its technologies, which are enhaunced to have a
> shared-nothing multi-master PostgreSQL-based database cluster.
>
> This first stable version is based on PostgreSQL 9.1.4. All the patches in
> PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of
> June 2012).
> This includes the security fix related to pg_crypto dated of 30th of May.
> You can download the source tarball directly from here:
> https://sourceforge.net/projects/postgres-xc/files/latest/download
> This tarball contains all the HTML and man documentation.
>
> 30 bug fixes have been made since release of beta2, with some notable
> enhancements:
> - Support for EXTENSION is fixed
> - Stabilization of the use of slave nodes in cluster
> - Fix of a bug related to read-only transactions, improving performance by
> 15%.
> - Support of compilation for MacOSX
> About the scalability of this release, Postgres-XC 1.0.0 scales to a
> factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5
> nodes using a benchmark called DBT-1.
>
> Compared to version Postgres-XC 0.9.7, the following features have been
> added:
> - Fast query shipping (FQS), quick identification of expressions in a
> query that can be pushed down to remote nodes
> - SERIAL types
> - TABLESPACE
> - Utility to clean up 2PC transactions in cluster (pgxc_clean)
> - Utility for initialization of GTM (global transaction manager, utility
> called initgtm)
> - Relation-size functions and locking functions
> - Regression stabilization
>
> The documentation of 1.0, including release notes, is available here:
> http://postgres-xc.sourceforge.net/docs/1_0/.
>
> The project can be followed on Source Forge:
> http://postgres-xc.sourceforge.net/.
> And a couple of GIT repositories are used for development:
> - SourceForge:
> http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
> - Github: https://github.com/postgres-xc/postgres-xc
>
> The core team is currently working in the addition of new features for the
> next major release including:
> - Merge with PostgreSQL 9.2
> - Data redistribution functionality, changing table distribution in
> cluster with a simple ALTER TABLE
> - New functionalities related to online node addition and deletion for a
> better user experience
> - Triggers
> - Planner improvements
> - Global constraints.
> The roadmap of the project is located here =>
> http://postgres-xc.sourceforge.net/ in section Roadmap.
>
> The project is under the same license as PostgreSQL, now managed under a
> single entity called "Postgres-XC Development Group".
> In order to keep in touch with the project, whose development follows the
> same model as PostgreSQL, you can register to the following mailing lists:
> - pos...@li..., for general questions.
> Registration can be done here:
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
> - pos...@li.... hachers mailing list.
> Registration can be done here:
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
> See you soon on the project mailing list, and have fun with this stable
> release.
> --
> Michael Paquier
> Member of core team of Postgres-XC, and Postgres-XC Development Group
>

question regarding the "--with-libxml" configure option during the install...

Does this mean that certain XML functions like XMLPARSE will not work unless I install with this option?



________________________________
From: Michael Vitale [mic...@ar...]
Sent: Thursday, June 07, 2012 10:06 AM
To: Michael Paquier; Postgres-XC mailing list; PostgreSQL mailing lists
Subject: Re: [Postgres-xc-general] Release of Postgres-XC 1.0.0

is there an RPM for 1.0.0, and if so, where?


________________________________
From: Michael Paquier [mic...@gm...]
Sent: Thursday, June 07, 2012 3:30 AM
To: Postgres-XC mailing list; PostgreSQL mailing lists
Subject: [Postgres-xc-general] Release of Postgres-XC 1.0.0

Hi all,

Postgres-XC, read&write-scalable multi-master symmetric cluster based on PostgreSQL, version 1.0.0 is released.
This project is seen as an open-source alternative to costly products such as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can naturally use all its technologies, which are enhaunced to have a shared-nothing multi-master PostgreSQL-based database cluster.

This first stable version is based on PostgreSQL 9.1.4. All the patches in PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of June 2012).
This includes the security fix related to pg_crypto dated of 30th of May.
You can download the source tarball directly from here:
https://sourceforge.net/projects/postgres-xc/files/latest/download
This tarball contains all the HTML and man documentation.

30 bug fixes have been made since release of beta2, with some notable enhancements:
- Support for EXTENSION is fixed
- Stabilization of the use of slave nodes in cluster
- Fix of a bug related to read-only transactions, improving performance by 15%.
- Support of compilation for MacOSX
About the scalability of this release, Postgres-XC 1.0.0 scales to a factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 nodes using a benchmark called DBT-1.

Compared to version Postgres-XC 0.9.7, the following features have been added:
- Fast query shipping (FQS), quick identification of expressions in a query that can be pushed down to remote nodes
- SERIAL types
- TABLESPACE
- Utility to clean up 2PC transactions in cluster (pgxc_clean)
- Utility for initialization of GTM (global transaction manager, utility called initgtm)
- Relation-size functions and locking functions
- Regression stabilization

The documentation of 1.0, including release notes, is available here:
http://postgres-xc.sourceforge.net/docs/1_0/.

The project can be followed on Source Forge: http://postgres-xc.sourceforge.net/.
And a couple of GIT repositories are used for development:
- SourceForge: http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
- Github: https://github.com/postgres-xc/postgres-xc

The core team is currently working in the addition of new features for the next major release including:
- Merge with PostgreSQL 9.2
- Data redistribution functionality, changing table distribution in cluster with a simple ALTER TABLE
- New functionalities related to online node addition and deletion for a better user experience
- Triggers
- Planner improvements
- Global constraints.
The roadmap of the project is located here => http://postgres-xc.sourceforge.net/ in section Roadmap.

The project is under the same license as PostgreSQL, now managed under a single entity called "Postgres-XC Development Group".
In order to keep in touch with the project, whose development follows the same model as PostgreSQL, you can register to the following mailing lists:
- pos...@li...<mailto:pos...@li...>, for general questions. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
- pos...@li...<mailto:pos...@li...>. hachers mailing list. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

See you soon on the project mailing list, and have fun with this stable release.
--
Michael Paquier
Member of core team of Postgres-XC, and Postgres-XC Development Group

is there an RPM for 1.0.0, and if so, where?


________________________________
From: Michael Paquier [mic...@gm...]
Sent: Thursday, June 07, 2012 3:30 AM
To: Postgres-XC mailing list; PostgreSQL mailing lists
Subject: [Postgres-xc-general] Release of Postgres-XC 1.0.0

Hi all,

Postgres-XC, read&write-scalable multi-master symmetric cluster based on PostgreSQL, version 1.0.0 is released.
This project is seen as an open-source alternative to costly products such as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can naturally use all its technologies, which are enhaunced to have a shared-nothing multi-master PostgreSQL-based database cluster.

This first stable version is based on PostgreSQL 9.1.4. All the patches in PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of June 2012).
This includes the security fix related to pg_crypto dated of 30th of May.
You can download the source tarball directly from here:
https://sourceforge.net/projects/postgres-xc/files/latest/download
This tarball contains all the HTML and man documentation.

30 bug fixes have been made since release of beta2, with some notable enhancements:
- Support for EXTENSION is fixed
- Stabilization of the use of slave nodes in cluster
- Fix of a bug related to read-only transactions, improving performance by 15%.
- Support of compilation for MacOSX
About the scalability of this release, Postgres-XC 1.0.0 scales to a factor of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 nodes using a benchmark called DBT-1.

Compared to version Postgres-XC 0.9.7, the following features have been added:
- Fast query shipping (FQS), quick identification of expressions in a query that can be pushed down to remote nodes
- SERIAL types
- TABLESPACE
- Utility to clean up 2PC transactions in cluster (pgxc_clean)
- Utility for initialization of GTM (global transaction manager, utility called initgtm)
- Relation-size functions and locking functions
- Regression stabilization

The documentation of 1.0, including release notes, is available here:
http://postgres-xc.sourceforge.net/docs/1_0/.

The project can be followed on Source Forge: http://postgres-xc.sourceforge.net/.
And a couple of GIT repositories are used for development:
- SourceForge: http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
- Github: https://github.com/postgres-xc/postgres-xc

The core team is currently working in the addition of new features for the next major release including:
- Merge with PostgreSQL 9.2
- Data redistribution functionality, changing table distribution in cluster with a simple ALTER TABLE
- New functionalities related to online node addition and deletion for a better user experience
- Triggers
- Planner improvements
- Global constraints.
The roadmap of the project is located here => http://postgres-xc.sourceforge.net/ in section Roadmap.

The project is under the same license as PostgreSQL, now managed under a single entity called "Postgres-XC Development Group".
In order to keep in touch with the project, whose development follows the same model as PostgreSQL, you can register to the following mailing lists:
- pos...@li...<mailto:pos...@li...>, for general questions. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
- pos...@li...<mailto:pos...@li...>. hachers mailing list. Registration can be done here: https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

See you soon on the project mailing list, and have fun with this stable release.
--
Michael Paquier
Member of core team of Postgres-XC, and Postgres-XC Development Group

Hi all,

Postgres-XC, read&write-scalable multi-master symmetric cluster based on
PostgreSQL, version 1.0.0 is released.
This project is seen as an open-source alternative to costly products such
as OracleRAC. Postgres-XC is based on the code of PostgreSQL, so it can
naturally use all its technologies, which are enhaunced to have a
shared-nothing multi-master PostgreSQL-based database cluster.

This first stable version is based on PostgreSQL 9.1.4. All the patches in
PostgreSQL 9.1 stable branch have been merged up to commit 873d1c1 (1st of
June 2012).
This includes the security fix related to pg_crypto dated of 30th of May.
You can download the source tarball directly from here:
https://sourceforge.net/projects/postgres-xc/files/latest/download
This tarball contains all the HTML and man documentation.

30 bug fixes have been made since release of beta2, with some notable
enhancements:
- Support for EXTENSION is fixed
- Stabilization of the use of slave nodes in cluster
- Fix of a bug related to read-only transactions, improving performance by
15%.
- Support of compilation for MacOSX
About the scalability of this release, Postgres-XC 1.0.0 scales to a factor
of 3 when compared to a standalone server PostgreSQL 9.1.3 on 5 nodes using
a benchmark called DBT-1.

Compared to version Postgres-XC 0.9.7, the following features have been
added:
- Fast query shipping (FQS), quick identification of expressions in a query
that can be pushed down to remote nodes
- SERIAL types
- TABLESPACE
- Utility to clean up 2PC transactions in cluster (pgxc_clean)
- Utility for initialization of GTM (global transaction manager, utility
called initgtm)
- Relation-size functions and locking functions
- Regression stabilization

The documentation of 1.0, including release notes, is available here:
http://postgres-xc.sourceforge.net/docs/1_0/.

The project can be followed on Source Forge:
http://postgres-xc.sourceforge.net/.
And a couple of GIT repositories are used for development:
- SourceForge:
http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary
- Github: https://github.com/postgres-xc/postgres-xc

The core team is currently working in the addition of new features for the
next major release including:
- Merge with PostgreSQL 9.2
- Data redistribution functionality, changing table distribution in cluster
with a simple ALTER TABLE
- New functionalities related to online node addition and deletion for a
better user experience
- Triggers
- Planner improvements
- Global constraints.
The roadmap of the project is located here =>
http://postgres-xc.sourceforge.net/ in section Roadmap.

The project is under the same license as PostgreSQL, now managed under a
single entity called "Postgres-XC Development Group".
In order to keep in touch with the project, whose development follows the
same model as PostgreSQL, you can register to the following mailing lists:
- pos...@li..., for general questions.
Registration can be done here:
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
- pos...@li.... hachers mailing list.
Registration can be done here:
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers

See you soon on the project mailing list, and have fun with this stable
release.
-- 
Michael Paquier
Member of core team of Postgres-XC, and Postgres-XC Development Group

On Fri, Jun 1, 2012 at 11:26 PM, Joshua D. Drake <jd...@co...>wrote:

>
> Hello,
>
> Alright so this is what I have going on right now. I have Drupal 7 up
> running on PostgreSQL 9.1 @ xc.commandprompt.com . I am currently trying
> to figure out a logical structure for menu items vs content.
>
> If anyone wants to start a discussion on that problem it would be a great
> help so I am not throwing work at a dart board that is going to be cleared
> at the end of the day.
>
Some menu items for download and documentation would be great.
For the time being documentation is stored here:
http://postgres-xc.sourceforge.net/docs/
But the structure is very basic, I just upload the html files generated.
There is no search functionality on the documentation generated either.

Regarding the download options, a menu with the list of versions and links
to download packages and tarballs would be great.
For the time being, the release is done by simply uploading with a source
tarball in sourceforge.
There is no plan to work on packages there, so assuming that some people
would work on rpm, debian, or whatever, a page redirecting to all the
possible downloads would be nice.

Then, in the About part, why not creating a menu with a couple of sub-items
like:
- quotes
- examples of configuration
- Q&A
- etc.

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

Hello,

Alright so this is what I have going on right now. I have Drupal 7 up 
running on PostgreSQL 9.1 @ xc.commandprompt.com . I am currently trying 
to figure out a logical structure for menu items vs content.

If anyone wants to start a discussion on that problem it would be a 
great help so I am not throwing work at a dart board that is going to be 
cleared at the end of the day.

Sincerely,

jD

-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

On 05/30/2012 01:10 PM, Joshua D. Drake wrote:
>
>
> Hello,
>
> I am about to setup a VM for a test Drupal instance to get a test site
> up. I was wondering if there were folks in the community that would like
> to help provide content so that the core team can determine if it is a
> direction they would like to go?

Alrighty then... looks like I have a weekend project.

Sincerely,

jD
https://lists.sourceforge.net/lists/listinfo/postgres-xc-general


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

Hello,

I am about to setup a VM for a test Drupal instance to get a test site 
up. I was wondering if there were folks in the community that would like 
to help provide content so that the core team can determine if it is a 
direction they would like to go?

Sincerely,

jD

Hi,

Installing flex/bison and performing a make clean, and configure solved my issues. Thanks Michael!

Regards,
Marcos

On May 29, 2012, at 7:13 PM, koi...@gm... wrote:

> Readline and libz are not installed by default in ubuntu 10.4.  As Michael pointed out, you should install them.  This is the same as building PostgreSQL binary from the scratch.
> 
> ---
> Koichi Suzuki
> 
> On 2012/05/30, at 7:57, Michael Paquier <mic...@gm...> wrote:
> 
>> 
>> 
>> On Wed, May 30, 2012 at 7:47 AM, Marcos Mendez <mar...@gm...> wrote:
>> Hi,
>> 
>> No I did not install those. I believe I read somewhere that I only needed that for source build straight from git. I installed flex and bison and ran configure and make, but no joy. I'm including the configure log.
>> XC code has the same library dependencies as postgres.
>> You need to install the same libraries depending on the options you specify at configure step.
>> 
>> Also try to clean up your tarball.
>> You should do a make clean, re-run configure, and try make once again.
>> -- 
>> 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