pg_repack 1.3.0-beta1
- This Release
- pg_repack 1.3.0-beta1
- Date
- Status
- Testing
- Latest Stable
- pg_repack 1.5.2 —
- Other Releases
- Abstract
- PostgreSQL module for data reorganization
- Description
- Reorganize tables in PostgreSQL databases with minimal locks
- Released By
- schmiddy
- License
- BSD
- Resources
- Special Files
- Tags
Extensions
- pg_repack 1.3.0-beta1
- Reorganize tables in PostgreSQL databases with minimal locks
Documentation
- release
- What to do to release pg_repack
README
Contents
pg_repack -- Reorganize tables in PostgreSQL databases with minimal locks
- Homepage: http://reorg.github.com/pg_repack
- Download: http://pgxn.org/dist/pg_repack/
- Development: https://github.com/reorg/pg_repack
- Bug Report: https://github.com/reorg/pg_repack/issues
- Mailing List: http://pgfoundry.org/mailman/listinfo/reorg-general
pg_repack is a PostgreSQL extension which lets you remove bloat from tables and indexes, and optionally restore the physical order of clustered indexes. Unlike CLUSTER and VACUUM FULL it works online, without holding an exclusive lock on the processed tables during processing. pg_repack is efficient to boot, with performance comparable to using CLUSTER directly.
Please check the documentation (in the doc directory or online) for installation and usage instructions.
All users of pg_reorg 1.1.9 or earlier, and pg_repack 1.2.0-beta1 or earlier, are urged to upgrade to the latest pg_repack version to fix a serious data corruption issue.
What about pg_reorg?
pg_repack is a fork of the pg_reorg project, which has proven hugely successful. Unfortunately new feature development on pg_reorg has slowed or stopped since late 2011.
pg_repack was initially released as a drop-in replacement for pg_reorg, addressing some of the shortcomings of the last pg_reorg version (such as support for PostgreSQL 9.2 and EXTENSION packaging) and known bugs.
pg_repack 1.2 introduces further new features (parallel index builds, ability to rebuild only indexes) and bugfixes. In some cases its behaviour may be different from the 1.1.x release so it shouldn't be considered a drop-in replacement: you are advised to check the documentation before upgrading from previous versions.