1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/contrib.sgml,v 1.8 2007/12/06 04:12:09 tgl Exp $ -->
<appendix id="contrib">
<title>Additional Supplied Modules</title>
<para>
This appendix contains information regarding the modules that
can be found in the <literal>contrib</literal> directory of the
<productname>PostgreSQL</> distribution.
These include porting tools, analysis utilities,
and plug-in features that are not part of the core PostgreSQL system,
mainly because they address a limited audience or are too experimental
to be part of the main source tree. This does not preclude their
usefulness.
</para>
<para>
When building from the source distribution, these modules are not built
automatically. You can build and install all of them by running
<screen>
<userinput>gmake</userinput>
<userinput>gmake install</userinput>
</screen>
in the <literal>contrib</literal> directory of a configured source tree;
or to build and install
just one selected module, do the same in that module's subdirectory.
Many of the modules have regression tests, which can be executed by
running
<screen>
<userinput>gmake installcheck</userinput>
</screen>
once you have a <productname>PostgreSQL</> server running. (Note that
<literal>gmake check</> is not supported; you must have an operational
database server to perform these tests, and you must have built and
installed the module(s) to be tested.)
</para>
<para>
If you are using a pre-packaged version of <productname>PostgreSQL</>,
these modules are typically made available as a separate subpackage,
such as <literal>postgresql-contrib</>.
</para>
<para>
Many modules supply new user-defined functions, operators, or types.
To make use of one of these modules, after you have installed the code
you need to register the new objects in the database
system by running the SQL commands in the <literal>.sql</> file
supplied by the module. For example,
<programlisting>
psql -d dbname -f <replaceable>SHAREDIR</>/contrib/<replaceable>module</>.sql
</programlisting>
Here, <replaceable>SHAREDIR</> means the installation's <quote>share</>
directory (<literal>pg_config --sharedir</> will tell you what this is).
In most cases the script must be run by a database superuser.
</para>
<para>
You need to run the <literal>.sql</> file in each database that you want
the module's facilities to be available in. Alternatively, run it in
database <literal>template1</> so that the module will be copied into
subsequently-created databases by default.
</para>
<para>
You can modify the first command in the <literal>.sql</> file to determine
which schema within the database the module's objects will be created in.
By default, they will be placed in <literal>public</>.
</para>
<para>
After a major-version upgrade of <productname>PostgreSQL</>, run the
installation script again, even though the module's objects might have
been brought forward from the old installation by dump and restore.
This ensures that any new functions will be available and any needed
corrections will be applied.
</para>
&adminpack;
&btree-gist;
&chkpass;
&cube;
&dblink;
&dict-int;
&dict-xsyn;
&earthdistance;
&fuzzystrmatch;
&hstore;
&intagg;
&intarray;
&isn;
&lo;
<ree;
&oid2name;
&pageinspect;
&pgbench;
&pgbuffercache;
&pgcrypto;
&pgfreespacemap;
&pgrowlocks;
&pgstandby;
&pgstattuple;
&pgtrgm;
&seg;
&contrib-spi;
&sslinfo;
&tablefunc;
&test-parser;
&tsearch2;
&uuid-ossp;
&vacuumlo;
&xml2;
</appendix>
|
