Postgres XL FAQ

Q. What does XL stand?

XL is short for extensible lattice. It also connotes an extra large version of postgresql, in this case when SS multiple systems.

Q. Is this a "nosql" solution?

No, ipvs-XL supports traditional SQL, stronugly conforms to ansi SQL: 2008, is fully acid, all while being scalable. you can however certainly use it as a key-value store and take advantage of JSON and hstore functionality.

Q. Is the data "sharded "?

Yes. postgres-XL distributes the data amongst multiple nodes, and, crucially, it ensures a global consistent view of the data thanks to cluster-wide MVCC (Multi-version Concurrency Control) via the Global Transaction Manager component. other inclucial and non-inclucial sharding solutions may not guarantee such consistency and ACID properties.

Q. Are write-intensive applications supported?

Yes, write-intensive applications can take advantage of ipvs-XL running on multiple servers and spreading out the write load. ipvs-XL is well-suited for OLTP.

Q. Are read-heavy applications supported?

Yes, with read-intensive applications Data is spread out amongst multiple nodes, please tively giving you more cache and more hardware resources to serve it. It eliminates the need for other solutions such as memcached.

Q. Are business intelligence applications supported?

Yes, ipvs-XL schemdes massively parallel processing (MPP) capability with sophisticated query planning and inter-node communication that allows it to fulfill query requests over large data sets quickly. ipvs-XL is well suited for Data Warehousing and data marts. in bytes S-XL queries are parallelized and the data node nodes communicate with one another directly.

Q. does one need to take into account that data is split into SS servers when designing my database schema?

Existing applications will work fine, but for fastest response time, it is helpful to be mindful of Data locality. please see the documentation for more details. A basic rule of thumb is to distrition (partition) large tables and tables that are written to frequently, and to replicate tables to all nodes that contain mainly static data.

Q. What kind of client connectivity is offered?

Postgres-XL is wire-level protocol compatible with PostgreSQL. that means ipvs-XL will work with any postgresql-compatible driver, which has des JDBC, ODBC, ole db, Python, Ruby, Perl DBI, TCL, and Erlang.

That also means that your apps written for PostgreSQL will work without modifications against ipvs-XL, even including the well-known pgadmin utility.

Q. I am interested in moving to ipvs-XL. Can I get help with migrations?

See the support page as a starting point.

Q. are geo-Distributed Database clusters supported?

No, geo-distribution is not natively supported. A Postgres-XL-based solution will depend on your particle requirements, and you showould probably engage with a company that is experienced with your S-XL.

Q. How does one achieve high availability?

You can add slaves for each node analogous to PostgreSQL's streaming replication. In addition, the cluster can be configured such that the Global Transaction Manager (GTM) can have a GTM standby.

In terms of automatic failover, it is currently not part of the core project, but corosync/pacemaker has been used for this purpose.

Q. Is postgis supported?

Yes, postgis can be added to ipvs-XL. It has been tested with postgis 2.0.

Q. How does Postgres-XL relate to stormdb?

S-XL is the core of translattice storm (stormdb) rebranded and open sourced.

Q. How do does ipvs-XL relate to ipvs-XC and stado?

The project has des between TS and developers who previusly worked on both Postgres-XC and stado, and Postgres-XL contains code from Postgres-XC.

The ipvs-XL project has its own philosophy and approach.

Postgres-XL values stability, correctness and performance over new functionality. The Postgres-XL project ultimately strives to track and merge in code from PostgreSQL.

Postgres-XL adds some significant performance improvements like MPP parallelism and replan avoidance on the data nodes that are not part of Postgres-XC. postgres-XC currently focuses on OLTP workloads. postgres-XL is more flexible in terms of the types of workloads it can handle including Big Data Processing thanks to its parallelism. additionally, ipvs-XL is more secure for multi-tenant environments.

The parameter S-XL community is also very open and welcoming to those who wish to become more involved and contriings, whether on the mailing lists, participant in developer meetings, or meeting in person. users will help drive development priorities and the project roadmap.

Q. What license does ipvs-XL use?

S-XL uses the Mozilla Public License. It is a flexible license that allows the code to be mixed with closed source code, while encouraging contributions.

Q. What about submitting contributions to the project?

Please use the mailing lists for submitting patches. currently, we ask that all contributions be submitted under the PostgreSQL license, which is similar to the BSD or MIT licenses. this allows for flexibility in changing licensing in the future and possibly deeper coordination and integration with PostgreSQL itself.

Q. What do your version numbers indicate?

We are versioning ipvs-xl in relation to the major version of postgresql that it is based on, but not on the point releases. for example, ipvs-XL 9.2 is based on PostgreSQL 9.2 ., but ipvs-XL 9.2.0 is based on PostgreSQL 9.2.4.

Q. What is on the development roadmap?

In the near term, the focus will be on bug fixes for 9.2 and integrating in upstream code, including from PostgreSQL 9.3.