@@ -35,7 +35,7 @@ doc/src/sgml/pgrepack.sgml
35
35
lets you remove bloat from tables and
36
36
indexes, and optionally restore the physical order of clustered
37
37
indexes. Unlike <xref linkend="sql-cluster">
38
- and <command>VACUUM_ FULL</command> it works online,
38
+ and <command>VACUUM FULL</command> it works online,
39
39
without holding an exclusive lock on
40
40
the processed tables during processing. <application>pg_repack</application>
41
41
is efficient to boot, with performance comparable to using <command>CLUSTER</command> directly.
@@ -77,56 +77,33 @@ doc/src/sgml/pgrepack.sgml
77
77
<title>Installation</title>
78
78
79
79
<para>
80
- <application>pg_repack</application> can be built with <application>make</application>
81
- on UNIX or Linux. The <acronym>PGXS</acronym> build framework is used automatically.
82
- Before building, you might need to install the <productname>&productname;</productname>
83
- development packages and add the directory containing <application>pg_config</application>
84
- to your <envar>PATH</envar>. Then you can run:
85
- <screen>
86
- $ cd pg_repack
87
- $ make
88
- $ sudo make install
89
- </screen>
90
- </para>
91
-
92
- <para>
93
- You can also use <productname>Microsoft Visual C++ 2010</productname> to build
94
- the program on <productname>Windows</productname>.
95
- There are project files in the <filename>msvc</filename> folder.
80
+ On Linux systems, <application>pg_repack</application> is provided together
81
+ with <productname>&project;</productname> as a separate pre-built package
82
+ and requires the <filename>postgrespro-&edn;-&majorversion;-server</filename>
83
+ package to be installed with all the dependencies. For the list of available
84
+ packages and detailed installation instructions, see <xref linkend="installation-bin">.
85
+ On Windows systems, <application>pg_repack</application> is automatically
86
+ installed as part of <productname>&project;</productname>.
96
87
</para>
97
88
98
89
<para>
99
- After installation, load the <filename>pg_repack</filename> extension
100
- in the database you want to process. On <productname>PostgreSQL</productname> 9.1
101
- and following <filename>pg_repack</filename> is packaged as an extension,
102
- so you can execute:
90
+ Once you have <application>pg_repack</application> installed,
91
+ load the <filename>pg_repack</filename> extension
92
+ in the database you want to process, as follows:
103
93
<screen>
104
94
$ psql -c "CREATE EXTENSION pg_repack" -d <replaceable>your_database</replaceable>
105
95
</screen>
106
96
</para>
107
97
108
98
<para>
109
- For previous <productname>PostgreSQL</productname> versions you should
110
- load the script <filename>$SHAREDIR/contrib/pg_repack.sql</filename>
111
- in the database to process; you can get <replaceable>$SHAREDIR</replaceable>
112
- using <command>pg_config --sharedir</command>, e.g.:
113
- <screen>
114
- $ psql -f "$(pg_config --sharedir)/contrib/pg_repack.sql" -d <replaceable>your_database</replaceable>
115
- </screen>
116
- </para>
117
-
118
- <para>
119
- You can remove <literal>pg_repack</literal> from
120
- a <productname>PostgreSQL</productname> 9.1 and following database
99
+ You can later remove <literal>pg_repack</literal> from
100
+ a <productname>&project;</productname> installation
121
101
using <literal>DROP EXTENSION pg_repack</literal>.
122
- For previous <productname>PostgreSQL</productname> versions load the
123
- <filename>$SHAREDIR/contrib/uninstall_pg_repack.sql</filename> script
124
- or just drop the <literal>repack</literal> schema.
125
102
</para>
126
103
127
104
<para>
128
- If you are upgrading from a previous version of <application>pg_repack</application>
129
- or <application>pg_reorg</application>, just drop the old version from the database
105
+ If you are upgrading from a previous version of <application>pg_repack</application>,
106
+ just drop the old version from the database
130
107
as explained above and install the new version.
131
108
</para>
132
109
</refsect1>
0 commit comments