|
1 | | -pg_repack -- Reorganize tables in PostgreSQL databases without any locks |
2 | | -======================================================================== |
| 1 | +pg_repack -- Reorganize tables in PostgreSQL databases with minimal locks |
| 2 | +========================================================================= |
3 | 3 |
|
4 | 4 | - Homepage: http://reorg.github.com/pg_repack |
5 | 5 | - Development: https://github.com/reorg/pg_repack |
6 | 6 | - Bug Report: https://github.com/reorg/pg_reorg/issues |
7 | 7 | - Mailing List: http://pgfoundry.org/mailman/listinfo/reorg-general |
8 | 8 |
|
9 | | -pg_repack_ is an utility program to reorganize tables in PostgreSQL databases. |
10 | | -Unlike clusterdb_, it doesn't block any selections and updates during |
11 | | -reorganization. |
| 9 | +pg_repack_ is a PostgreSQL extension which lets you remove bloat from |
| 10 | +tables and indexes, and optionally restore the physical order of clustered |
| 11 | +indexes. Unlike CLUSTER_ and `VACUUM FULL`_ it works online, without |
| 12 | +holding an exclusive lock on the processed tables during processing. |
| 13 | +pg_repack is efficient to boot, with performance comparable to using |
| 14 | +CLUSTER directly. |
12 | 15 |
|
13 | 16 | Please check the documentation (in the ``doc`` directory or online_) for |
14 | 17 | installation and usage instructions. |
15 | 18 |
|
16 | 19 | .. _pg_repack: http://reorg.github.com/pg_repack |
17 | | -.. _clusterdb: http://www.postgresql.org/docs/current/static/app-clusterdb.html |
| 20 | +.. _CLUSTER: http://www.postgresql.org/docs/current/static/sql-cluster.html |
| 21 | +.. _VACUUM FULL: VACUUM_ |
| 22 | +.. _VACUUM: http://www.postgresql.org/docs/current/static/sql-vacuum.html |
18 | 23 | .. _online: pg_repack_ |
19 | 24 |
|
20 | 25 |
|
21 | 26 | What about pg_reorg? |
22 | 27 | -------------------- |
23 | 28 |
|
24 | 29 | 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. |
| 30 | +successful. Unfortunately the last version of pg_reorg was 1.1.7, released |
| 31 | +in Aug. 2011, and development of the project has stagnated since then. The |
| 32 | +first release of pg_repack contains many key improvements which have been |
| 33 | +missing from pg_reorg (e.g. support for PostgreSQL 9.2, and EXTENSION |
| 34 | +packaging). |
| 35 | + |
| 36 | +In an effort to make the transition for existing pg_reorg users simple, and |
| 37 | +facilitate a possible merge back with pg_reorg, we are releasing |
| 38 | +pg_repack 1.1.8 as a drop-in replacement for pg_reorg, addressing the |
| 39 | +pg_reorg 1.1.7 bugs and shortcomings. We are also developing new features |
| 40 | +to be released in an upcoming 1.2 version. pg_repack may be an interim |
| 41 | +solution, should the pg_reorg project come back to life. |
| 42 | + |
| 43 | +In the meantime, we thank the original pg_reorg authors for the quality code |
| 44 | +they have released to the community, wish them good luck, and hope to |
| 45 | +collaborate further in the future. |
40 | 46 |
|
41 | 47 | .. _pg_reorg: http://reorg.projects.pgfoundry.org/ |
0 commit comments