Releases: citusdata/pg_shard
v1.2.3
pg_shard v1.2 introduced the use of SPI in the metadata system to better abstract differences between pg_shard and CitusDB representations of distribution metadata. This release addresses performance issues from that change by ensuring SPI plans are cached after their first use.
v1.2.2
The use_citusdb_select_logic configuration parameter defaults to false, which was causing confusion now that pg_shard sees and understands all CitusDB metadata. This release changes the default to true when pg_shard is compiled and installed against CitusDB rather than PostgreSQL.
v1.2.1
Fixes a bug triggered by updating from an older pg_shard version within CitusDB when distributed tables already exist.
v1.2.0
When installed within CitusDB, pg_shard will automatically synchronize metadata about table distribution to the catalog tables used by CitusDB. Additionally, users can use enumeration or composite types as partition columns and will appreciate minor improvements in error messages and input checking.
v1.1.1
Fixes a bug triggered by repairing shard placements belonging to a table that makes use of indexes.
v1.1.0
The sophomore release of pg_shard brings several new features as well as a better user experience, enhanced performance, and improved resource utilization. In addition to an up to fourfold improvement in INSERT speed, users can benefit from a new shard repair function, a script to make bulk data loads easier, and on-demand metadata synchronization with CitusDB.
v1.0.2
v1.0.1
v1.0.0
Initial release of pg_shard, a transparent sharding extension for PostgreSQL. pg_shard enables your tables and queries to be distributed across any number of PostgreSQL servers without requiring any changes to your application code.
Supports single-shard INSERT, UPDATE, and DELETE as well as multi-shard SELECT queries.