sumedhpathak

Distributing Postgres with a Distributed Team at Citus Data

Over the last two years, our engineering team at Citus Data has shortened release cycles from 12 months all the way down to 8 weeks. The most recent 7.2 release of the Citus database took 8 weeks exactly, start to finish.

These shortened release cycles have been chock full of new capabilities for our users, including distributed deadlock detection in Citus 7.0, multi-shard updates and deletes in Citus 7.1, and support for CTE’s (common table expressions) and complex Postgres subqueries in Citus 7.2.

On the Citus Cloud side (that’s our fully-managed database as a service that runs on AWS), we’ve recently added fork, followers, fully-online “warp” migration from existing PostgreSQL installations, and point-in-time-recovery (PITR), just to name

sumedhpathak

Steps for hash-partitioning on composite types

• Create the type on the master and all worker nodes:

CREATE TYPE new_composite_type as (project_key text, date text);

• Create a function for checking equality, and associate it with the equality operator for the new type