Distributed PostgreSQL as an extension
 
 
 
 
 
 
Go to file
Jason Petersen abe7304898
Support SERIAL/BIGSERIAL non-partition columns
This adds support for SERIAL/BIGSERIAL column types. Because we now can
evaluate functions on the master (during execution), adding this is a
matter of ensuring the table creation step works properly.

To accomplish this, I've added some logic to detect sequences owned by
a table (i.e. those related to its columns). Simply creating a sequence
and using it in a default value is insufficient; users who do so must
ensure the sequence is owned by the column using it.

Fortunately, this is exactly what SERIAL and BIGSERIAL do, which is the
use case we're targeting with this feature. While testing this, I found
that worker_apply_shard_ddl_command actually adds shard identifiers to
sequence names, though I found no places that use or test this path. I
removed that code so that sequence names are not mutated and will match
those used by a SERIAL default value expression.

Our use of the new-to-9.5 CREATE SEQUENCE IF NOT EXISTS syntax means we
are dropping support for 9.4 (which is being done regardless, but makes
this change simpler). I've removed 9.4 from the Travis build matrix.

Some edge cases are possible in ALTER SEQUENCE, COPY FROM (on workers),
and CREATE SEQUENCE OWNED BY. I've added errors for each so that users
understand when and why certain operations are prohibited.
2016-07-28 23:55:40 -06:00
src Support SERIAL/BIGSERIAL non-partition columns 2016-07-28 23:55:40 -06:00
.gitattributes Switch to using git attributes to ignore files 2016-02-15 23:41:51 -07:00
.gitignore Initial commit of Citus 5.0 2016-02-11 04:05:32 +02:00
.travis.yml Remove PostgreSQL 9.4 support 2016-07-26 20:16:09 +03:00
CHANGELOG.md Add CHANGELOG entries for 5.1.1 release 2016-06-17 16:03:32 -06:00
CONTRIBUTING.md Proper indentation for code blocks in lists 2016-03-30 15:40:53 -07:00
LICENSE Add AGPL-3.0 in LICENSE file 2016-03-23 17:04:58 -06:00
Makefile Fix various build issues 2016-03-11 13:38:47 -07:00
Makefile.global.in Detect flex in citus configure script, instead of relying postgres'. 2016-06-22 11:03:22 -07:00
README.md Update docs links (#663) 2016-07-21 13:39:40 -07:00
autogen.sh Changed product name to citus 2016-02-15 16:04:31 +02:00
configure Remove PostgreSQL 9.4 support 2016-07-26 20:16:09 +03:00
configure.in Remove PostgreSQL 9.4 support 2016-07-26 20:16:09 +03:00
github-banner.png Readme for 5.0 2016-03-18 13:32:13 -07:00
prep_buildtree Changed product name to citus 2016-02-15 16:04:31 +02:00

README.md

Citus Banner

Build Status Slack Status Latest Docs

What is Citus?

  • Open-source PostgreSQL extension (not a fork)
  • Scalable across multiple hosts through sharding and replication
  • Distributed engine for query parallelization
  • Highly available in the face of host failures

Citus horizontally scales PostgreSQL across commodity servers using sharding and replication. Its query engine parallelizes incoming SQL queries across these servers to enable real-time responses on large datasets.

Citus extends the underlying database rather than forking it, which gives developers and enterprises the power and familiarity of a traditional relational database. As an extension, Citus supports new PostgreSQL releases, allowing users to benefit from new features while maintaining compatibility with existing PostgreSQL tools. Note that Citus supports many (but not all) SQL commands; see the FAQ for more details.

Common Use-Cases:

  • Powering real-time analytic dashboards
  • Exploratory queries on events as they happen
  • Large dataset archival and reporting
  • Session analytics (funnels, segmentation, and cohorts)

To learn more, visit citusdata.com and join the mailing list to stay on top of the latest developments.

Quickstart

Local Citus Cluster

  • Install docker-compose: Mac | Linux

  • (Mac only) connect to Docker VM

    eval $(docker-machine env default)
    
  • Pull and start the docker images

    wget https://raw.githubusercontent.com/citusdata/docker/master/docker-compose.yml
    docker-compose -p citus up -d
    
  • Connect to the master database

    docker exec -it citus_master psql -U postgres -d postgres
    
  • Follow the first tutorial instructions

  • To shut the cluster down, run

    docker-compose -p citus down
    

Talk to Contributors and Learn More

Documentation Try the Citus tutorials for a hands-on introduction or
the documentation for a more comprehensive reference.
Google Groups The Citus Google Group is our place for detailed questions and discussions.
Slack Chat with us in our community Slack channel.
Github Issues We track specific bug reports and feature requests on our project issues.
Twitter Follow @citusdata for general updates and PostgreSQL scaling tips.
Training and Support See our support page for training and dedicated support options.

Contributing

Citus is built on and of open source. We welcome your contributions, and have added a helpwanted label to issues which are accessible to new contributors. The CONTRIBUTING.md file explains how to get started developing the Citus extension itself and our code quality guidelines.

Who is Using Citus?

Citus is deployed in production by many customers, ranging from technology start-ups to large enterprises. Here are some examples:

  • CloudFlare uses Citus to provide real-time analytics on 100 TBs of data from over 4 million customer websites. Case Study
  • MixRank uses Citus to efficiently collect and analyze vast amounts of data to allow inside B2B sales teams to find new customers. Case Study
  • Neustar builds and maintains scalable ad-tech infrastructure that counts billions of events per day using Citus and HyperLogLog.
  • Agari uses Citus to secure more than 85 percent of U.S. consumer emails on two 6-8 TB clusters. Case Study
  • Heap uses Citus to run dynamic funnel, segmentation, and cohort queries across billions of users and tens of billions of events. Watch Video

Copyright © 20122016 Citus Data, Inc.