Home

pg_reorg - Project Organization

The pg_reorg developers are slowly moving the project from its old home on pgfoundry to github. The current stable release of pg_reorg is 1.1.7. The project mailing list is hosted on pgfoundry at reorg-general. Please report bugs on the github issue tracker.

Official documentation page: pg_reorg, though this wiki page may serve as an unofficial documentation point.

Please help keep this wiki page up-to-date!

Why use pg_reorg?

pg_reorg is handy when you have a large table which has become bloated (see Show database bloat for a useful bloat-detection query). If you are able to hold an AccessExclusive lock on the table for an extended period, you have it easy: just use CLUSTER or VACUUM FULL. However, if your table is busy being accessed by queries which can't wait hours while a CLUSTER or VACUUM FULL completes, you need a solution which will de-bloat your table and indexes while allowing concurrent reads and writes of the table. pg_reorg allows you to do precisely this. See also depesz's summary.

Pending Features, Bugs, Known issues, Wishlist...

The current list is in the bug tracker.

A few features have been added to cvs, git master or another git branch, and are not yet in a stable release. Items are not fully categorized and should receive a milestone.