Citus BlogCitus Blog

PG Conf Silicon Valley is happening again this year in November and we're looking to make it even better and more informative than last year. To do that we're looking to you, both as an attendee and to come speak. We've already received a lot of great...

In the recent 5.1 release of the Citus extension for PostgreSQL, we added the ability to use the COPY command to load data into distributed tables. PostgreSQL's COPY command is one of the most powerful bulk loading features of any database and it is even more powerful on distributed tables.

PostgreSQL is known for its great extensibility and powerful plugins. One particular category of extensions is Foreign Data Wrappers or FDWs. FDWs allow us to interact from within Postgres directly with other data stores such as hdfs, columnar stores, mysql, etc. Combined with Citus’ scalability features, we can even leverage them to help us scale out those data stores where might otherwise be quite difficult.

At Citus we want to make dealing with large amounts of operational and analytical workloads easier. Data ingestion speed is key, being the necessary first step in working with any new database. Moreover ingestion is something you'll do repeatedly in testing and development so the bulk-loading user experience is important as well. With the release of Citus 5.1 the experience in loading data is much better all around, and we’ve managed to sneak in a few other improvements as well. Read more below or give it a try today.

Product search is a common, yet sometimes challenging use-case for online retailers and marketplaces. It typically involves a combination of full-text search and filtering by attributes which differ for every product category. More complex use-cases may have many sellers that offer the same product, but with a different price and different properties.

At Citus we believe in making databases easier. Key to that is empowering users to scale Postgres beyond the typical limits of a single node. Our latest Citus release makes it easier than ever to scale memory and processors while retaining access to familiar SQL queries and rich Postgres features. But database management can be tricky even in the single-node case, so we at Citus have been hard at work building the next step in our journey to make databases easier: Citus Cloud, an on-demand cloud service on top of Amazon Web Services available today in private beta. *Citus Cloud is now fully GA, you can learn more here

The following post is contributed by 8Kdata

An introduction to pg_paxos

Pg_paxos is a database level implementation of the widely renowned Paxos protocol, invented by Leslie Lamport. Pg_paxos offers a master-less (or multi-master, if you prefer) layer that can be enabled directly in the database without the need for external tools or transaction managers.

It may surprise you that pagination, pervasive as it is in web applications, is easy to implement inefficiently. In this article we'll examine several methods of server-side pagination and discuss their tradeoffs when implemented in PostgreSQL. This article will help you identify which technique is appropriate for your situation, including some you may not have seen before which rely on physical clustering and the database stats collector.

When we started working on CitusDB 1.0 four years ago, we envisioned scaling out relational databases. We loved Postgres (and the elephant) and picked it as our underlying database of choice. Our goal was to extend this database to seamlessly shard

With the Citus extension, you can use PostgreSQL to build applications that interactively query large data sets, for example analytical dashboards. At the same time, you can keep adding new data at high rates and use PostgreSQL's powerful indexing...