Displaying 1 to 8 from 8 results

pg_partman - Partition management extension for PostgreSQL

  •    PLpgSQL

pg_partman is an extension to create and manage both time-based and serial-based table partition sets. Native partitioning in PostgreSQL 10 is supported as of pg_partman v3.0.1. Note that all the features of trigger-based partitioning are not yet supported in native, but performance in both reads & writes is significantly better. Child table creation is all managed by the extension itself. For non-native, trigger function maintenance is also handled. For non-native partitioning, tables with existing data can have their data partitioned in easily managed smaller batches. For native partitioning, the creation of a new partitioned set is required and data will have to be migrated over separately.

pg_pathman - Partitioning tool for PostgreSQL

  •    C

The pg_pathman module provides optimized partitioning mechanism and functions to manage partitions. Take a look at our Wiki out there.

zabbix-pgsql-partitioning - Partitioning scripts for Zabbix on PostgreSQL

  •    PLpgSQL

Scripts for partitioning the Zabbix database on PostgreSQL.These scripts cater for partitioning any Zabbix tables that include the clock column.

alpine-linux-scripts - Alpine Linux Setup Scripts

  •    Shell

To install to gpt disks you will need to choose a (b)oot disk layout in setup-partitions for the boot drive to be confgured correctly.

pucket - Bucketing and partitioning system for Parquet

  •    Scala

Parquet + Bucket = Pucket. Pucket is Scala library which provides a simple partitioning system for Parquet.

shards - Transparent and out-of-box Sharding support for Erlang/Elixir ETS tables!

  •    Erlang

Sharding support for ETS tables out-of-box. Why might we need Sharding on ETS tables? Well, the main reason is to keep the lock contention under control, in order to scale-out ETS tables (linearly) and support higher levels of concurrency without lock issues; specially write-locks, which most of the cases might cause significant performance degradation.

pg_shardman - PostgreSQL sharding built on partitioning, postgres_fdw and logical replication

  •    Python

pg_shardman is a PG 11 experimental extenstion which explores applicability of Postgres partitioning, postgres_fdw and logical replication for sharding. It allows to hash-shard tables using pg_pathman and move the shards across nodes, balancing read/write load. You can issue queries to any node, postgres_fdw is responsible for redirecting them to the proper one. To avoid data loss, we support replication of partitions via synchronous or asynchronous logical replication (LR), redundancy level is configurable. Manual failover is provided. While pg_shardman can be used with vanilla PostgreSQL 11, some features require patched core. Most importantly, to support sane cross-node transactions, we use patched postgres_fdw with 2PC for atomicity and distributed snapshot manager providing snapshot isolation level of xact isolation. We support current version here, which we call 'patched Postgres' in this document. To manage the cluster, we need one designated PG node which we call shardlord. This node accepts sharding commands (implemented as usual PG functions) from the user and makes sure the whole cluster changes its state as desired. Shardlord holds several tables (see below) forming cluster metadata -- which nodes are in cluster and which partitions they keep. Currently shardlord can't keep sharded data itself and is manually configured by the administrator. We will refer to the rest of the nodes as worker nodes or workers.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.