pg_repack is an unofficial fork from the now abandoned pg_org project.
As the original pg_org extension, pg_repack does not lock any tables when moving data around and can be used to optimize production level databases.
pg_repack comes with three distinct methods for reorganizing the table and one specific method for restructuring the indexes.
What is new in this release:
- Added --tablespace and --moveidx options to perform online SET TABLESPACE.
- Added --index to repack indexes only.
- Added --jobs option for parallel operation.
- Don't require --no-order to perform a VACUUM FULL on non-clustered tables.
- Don't wait for locks held in other databases.
- Bugfix: correctly handle key indexes with options such as DESC, NULL FIRST/LAST, COLLATE.
- Fixed data corruption bug on delete.
What is new in version 1.3.1:
- Added --tablespace and --moveidx options to perform online SET TABLESPACE.
- Added --index to repack indexes only.
- Added --jobs option for parallel operation.
- Don't require --no-order to perform a VACUUM FULL on non-clustered tables.
- Don't wait for locks held in other databases.
- Bugfix: correctly handle key indexes with options such as DESC, NULL FIRST/LAST, COLLATE.
- Fixed data corruption bug on delete.
What is new in version 1.1.8:
- New:
- Added support for PostgreSQL 9.2.
- Added support for CREATE EXTENSION on PostgreSQL 9.1 and following.
- Give user feedback while waiting for transactions to finish.
- Bugfix:
- Allow running on newly promoted streaming replication slaves.
- Fixed interaction between pg_repack and Slony 2.0/2.1.
- Properly escape column names.
- Avoid recreating invalid indexes, or choosing them as key.
Requirements:
- PostgreSQL 8.3 or higher
Limitations:
- Lots of disk space is used for reorganizing the database. If a database is 1 GB large, then an extra 2 GB is needed to run pg_repack.
評論沒有發現