Skip to content

Commit dd72e2a

Browse files
committed
Clarifying the pg_repack scope and its relation with pg_reorg
1 parent 6f8a8ba commit dd72e2a

File tree

1 file changed

+24
-7
lines changed

1 file changed

+24
-7
lines changed

README.rst

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,32 @@ pg_repack_ is an utility program to reorganize tables in PostgreSQL databases.
1010
Unlike clusterdb_, it doesn't block any selections and updates during
1111
reorganization.
1212

13-
pg_repack is a fork of the previous pg_reorg_ project. It was founded to
14-
gather the bug fixes and new development ideas that the slow pace of
15-
development of pg_reorg was struggling to satisfy.
13+
Please check the documentation (in the ``doc`` directory or online_) for
14+
installation and usage instructions.
1615

1716
.. _pg_repack: http://reorg.github.com/pg_repack
1817
.. _clusterdb: http://www.postgresql.org/docs/current/static/app-clusterdb.html
19-
.. _pg_reorg: http://reorg.projects.pgfoundry.org/
18+
.. _online: pg_repack_
2019

21-
Please check the documentation (in the ``doc`` directory or online_) for
22-
installation and usage instructions.
2320

24-
.. _online: pg_repack_
21+
What about pg_reorg?
22+
--------------------
23+
24+
pg_repack is a fork of the pg_reorg_ project, which has proven hugely
25+
successful; unfortunately its development has somewhat stagnated after the
26+
release 1.1.7, with several issues still open (support for PostgreSQL 9.2,
27+
EXTENSION, and several bugs to be fixed). After initial consultation with the
28+
pg_reorg authors, who showed interest in adopting more up-to-date development
29+
tools to receive and encourage collaboration, no further news has been
30+
received from them. In the meantime we are releasing pg_repack 1.1.8 as a
31+
drop-in replacement for pg_reorg, addressing the pg_reorg 1.1.7 bugs and
32+
shortcomings and developing new features to be release in a future 1.2
33+
version. pg_repack may be an interim solution, should the pg_reorg project
34+
come back to activity.
35+
36+
In the meantime, not having received further news from the pg_reorg authors,
37+
we wish everything is fine with them, we thank them for the quality code they
38+
have released to the community, and wish them good luck, in the hope to hear
39+
from them again.
40+
41+
.. _pg_reorg: http://reorg.projects.pgfoundry.org/

0 commit comments

Comments
 (0)