A few tweaks to the README, addressing the state of pg_reorg.

This commit is contained in:
schmiddy 2014-05-22 15:08:39 -04:00
parent 3ca9c39dff
commit 9916c48138

View File

@ -28,20 +28,18 @@ What about pg_reorg?
-------------------- --------------------
pg_repack is a fork of the pg_reorg_ project, which has proven hugely pg_repack is a fork of the pg_reorg_ project, which has proven hugely
successful. Unfortunately development appears to have stopped after the successful. Unfortunately new feature development on pg_reorg_ has slowed
release of the version 1.1.7, around August 2011. or stopped since late 2011.
pg_repack 1.1.8 was released as a drop-in replacement for pg_reorg, addressing pg_repack was initially released as a drop-in replacement for pg_reorg,
some of the shortcomings of the last pg_reorg version (such as support for addressing some of the shortcomings of the last pg_reorg version (such as
PostgreSQL 9.2 and EXTENSION packaging) and known bugs. Shortly after the support for PostgreSQL 9.2 and EXTENSION packaging) and known bugs.
first pg_repack release, pg_reorg 1.1.8 was released too, merging all the
pg_repack changes. Version 1.1.8 is the last pg_reorg release at the time of
writing.
pg_repack 1.2 is a new development line based on the original pg_reorg pg_repack 1.2 introduces further new features (parallel index builds,
codebase and offering new features. Its behaviour may be different from the ability to rebuild only indexes) and bugfixes. In some cases its behaviour
1.1.x release so it shouldn't be considered a drop-in replacement: you are may be different from the 1.1.x release so it shouldn't be considered a
advised to check the documentation__ before upgrading from previous versions. drop-in replacement: you are advised to check the documentation__ before
upgrading from previous versions.
.. __: pg_repack_ .. __: pg_repack_
.. _pg_reorg: http://reorg.projects.pgfoundry.org/ .. _pg_reorg: http://reorg.projects.pgfoundry.org/