1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Post-Installation Setup</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 HREF="mailto:pgsql-docs@postgresql.org"><LINK
12 TITLE="PostgreSQL 7.4.1 Documentation"
13 HREF="index.html"><LINK
15 TITLE=" Installation Instructions"
16 HREF="installation.html"><LINK
18 TITLE="Installation Procedure"
19 HREF="install-procedure.html"><LINK
21 TITLE="Supported Platforms"
22 HREF="supported-platforms.html"><LINK
25 HREF="stylesheet.css"><META
27 CONTENT="2003-12-22T03:48:47"></HEAD
33 SUMMARY="Header navigation table"
43 >PostgreSQL 7.4.1 Documentation</TH
51 HREF="install-procedure.html"
60 HREF="installation.html"
67 >Chapter 14. Installation Instructions</TD
73 HREF="installation.html"
81 HREF="supported-platforms.html"
96 >14.6. Post-Installation Setup</A
104 >14.6.1. Shared Libraries</A
110 > On some systems that have shared libraries (which most systems do)
111 you need to tell your system how to find the newly installed
112 shared libraries. The systems on which this is
119 > necessary include <SPAN
156 > The method to set the shared library search path varies between
157 platforms, but the most widely usable method is to set the
158 environment variable <TT
176 CLASS="PROGRAMLISTING"
177 >LD_LIBRARY_PATH=/usr/local/pgsql/lib
178 export LD_LIBRARY_PATH</PRE
188 CLASS="PROGRAMLISTING"
189 >setenv LD_LIBRARY_PATH /usr/local/pgsql/lib</PRE
193 >/usr/local/pgsql/lib</TT
194 > with whatever you set
202 HREF="install-procedure.html#CONFIGURE"
205 You should put these commands into a shell start-up file such as
213 good information about the caveats associated with this method can
215 HREF="http://www.visi.com/~barr/ldpath.html"
217 >http://www.visi.com/~barr/ldpath.html</A
221 > On some systems it might be preferable to set the environment
253 > If in doubt, refer to the manual pages of your system (perhaps
261 on get a message like
264 >psql: error in loading shared libraries
265 libpq.so.2.1: cannot open shared object file: No such file or directory</PRE
267 then this step was necessary. Simply take care of it then.
284 and you have root access you can run
286 CLASS="PROGRAMLISTING"
287 >/sbin/ldconfig /usr/local/pgsql/lib</PRE
289 (or equivalent directory) after installation to enable the
290 run-time linker to find the shared libraries faster. Refer to the
294 > for more information. On
306 CLASS="PROGRAMLISTING"
307 >/sbin/ldconfig -m /usr/local/pgsql/lib</PRE
309 instead. Other systems are not known to have an equivalent
319 >14.6.2. Environment Variables</A
325 > If you installed into <TT
327 >/usr/local/pgsql</TT
329 location that is not searched for programs by default, you should
332 >/usr/local/pgsql/bin</TT
333 > (or whatever you set
341 HREF="install-procedure.html#CONFIGURE"
347 >. Strictly speaking, this is not
348 necessary, but it will make the use of <SPAN
352 much more convenient.
355 > To do this, add the following to your shell start-up file, such as
363 want it to affect every user):
365 CLASS="PROGRAMLISTING"
366 >PATH=/usr/local/pgsql/bin:$PATH
375 >, then use this command:
377 CLASS="PROGRAMLISTING"
378 >set path = ( /usr/local/pgsql/bin $path )</PRE
386 To enable your system to find the <SPAN
390 documentation, you need to add lines like the following to a
391 shell start-up file unless you installed into a location that is
394 CLASS="PROGRAMLISTING"
395 >MANPATH=/usr/local/pgsql/man:$MANPATH
400 > The environment variables <TT
407 specify to client applications the host and port of the database
408 server, overriding the compiled-in defaults. If you are going to
409 run client applications remotely then it is convenient if every
410 user that plans to use the database sets <TT
414 is not required, however: the settings can be communicated via command
415 line options to most client programs.
424 SUMMARY="Footer navigation table"
435 HREF="install-procedure.html"
453 HREF="supported-platforms.html"
463 >Installation Procedure</TD
469 HREF="installation.html"
477 >Supported Platforms</TD