2 PostgreSQL Installation Instructions
4 This document describes the installation of PostgreSQL from the source code
7 -------------------------------------------------------------------------------
16 mkdir /usr/local/pgsql/data
17 chown postgres /usr/local/pgsql/data
19 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
20 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 &
21 /usr/local/pgsql/bin/createdb test
22 /usr/local/pgsql/bin/psql test
24 The long version is the rest of this document.
26 -------------------------------------------------------------------------------
30 In general, a modern Unix-compatible platform should be able to run PostgreSQL.
31 The platforms that had received specific testing at the time of release are
32 listed in the Section called Supported Platforms below. In the "doc"
33 subdirectory of the distribution there are several platform-specific FAQ
34 documents you might wish to consult if you are having trouble.
35 The following software packages are required for building PostgreSQL:
37 * GNU make is required; other make programs will *not* work. GNU make is
38 often installed under the name "gmake"; this document will always refer
39 to it by that name. (On some systems GNU make is the default tool with
40 the name "make".) To test for GNU make enter
44 It is recommended to use version 3.76.1 or later.
46 * You need an ISO/ANSI C compiler. Recent versions of GCC are
47 recommendable, but PostgreSQL is known to build with a wide variety of
48 compilers from different vendors.
50 * gzip is needed to unpack the distribution in the first place. If you are
51 reading this, you probably already got past that hurdle.
53 * The GNU Readline library (for comfortable line editing and command
54 history retrieval) will be used by default. If you don't want to use it
55 then you must specify the "--without-readline" option for "configure".
56 (On NetBSD, the "libedit" library is readline-compatible and is used if
57 "libreadline" is not found.)
59 * To build on Windows NT or Windows 2000 you need the Cygwin and cygipc
60 packages. See the file "doc/FAQ_MSWIN" for details.
62 The following packages are optional. They are not required in the default
63 configuration, but they are needed when certain build options are enabled, as
66 * To build the server programming language PL/Perl you need a full Perl
67 installation, including the "libperl" library and the header files. Since
68 PL/Perl will be a shared library, the "libperl" library must be a shared
69 library also on most platforms. This appears to be the default in recent
70 Perl versions, but it was not in earlier versions, and in general it is
71 the choice of whomever installed Perl at your site.
72 If you don't have the shared library but you need one, a message like
73 this will appear during the build to point out this fact:
75 *** Cannot build PL/Perl because libperl is not a shared library.
76 *** You might have to rebuild your Perl installation. Refer to
77 *** the documentation for details.
79 (If you don't follow the on-screen output you will merely notice that the
80 PL/Perl library object, "plperl.so" or similar, will not be installed.)
81 If you see this, you will have to rebuild and install Perl manually to be
82 able to build PL/Perl. During the configuration process for Perl, request
85 * To build the Python interface module or the PL/Python server programming
86 language, you need a Python installation, including the header files.
87 Since PL/Python will be a shared library, the "libpython" library must be
88 a shared library also on most platforms. This is not the case in a
89 default Python installation.
90 If after building and installing you have a file called "plpython.so"
91 (possibly a different extension), then everything went well. Otherwise
92 you should have seen a notice like this flying by:
94 *** Cannot build PL/Python because libpython is not a shared library.
95 *** You might have to rebuild your Python installation. Refer to
96 *** the documentation for details.
98 That means you have to rebuild (part of) your Python installation to
99 supply this shared library.
100 The catch is that the Python distribution or the Python maintainers do
101 not provide any direct way to do this. The closest thing we can offer you
102 is the information in Python FAQ 3.30. On some operating systems you
103 don't really have to build a shared library, but then you will have to
104 convince the PostgreSQL build system of this. Consult the "Makefile" in
105 the "src/pl/plpython" directory for details.
107 * If you want to build Tcl or Tk components (clients and the PL/Tcl
108 language) you of course need a Tcl installation.
110 * To build the JDBC driver, you need Ant 1.5 or higher and a JDK. Ant is a
111 special tool for building Java-based packages. It can be downloaded from
113 If you have several Java compilers installed, it depends on the Ant
114 configuration which one gets used. Precompiled Ant distributions are
115 typically set up to read a file ".antrc" in the current user's home
116 directory for configuration. For example, to use a different JDK than the
117 default, this may work:
119 JAVA_HOME=/usr/local/sun-jdk1.3
120 JAVACMD=$JAVA_HOME/bin/java
122 Note: Do not try to build the driver by calling "ant" or even
123 "javac" directly. This will not work. Run "gmake" normally as
126 * To enable Native Language Support (NLS), that is, the ability to display
127 a program's messages in a language other than English, you need an
128 implementation of the Gettext API. Some operating systems have this
129 built-in (e.g., Linux, NetBSD, Solaris), for other systems you can
130 download an add-on package from here: http://www.postgresql.org/~petere/
131 gettext.html. If you are using the gettext implementation in the GNU C
132 library then you will additionally need the GNU Gettext package for some
133 utility programs. For any of the other implementations you will not need
136 * Kerberos, OpenSSL, or PAM, if you want to support authentication using
139 If you are build from a CVS tree instead of using a released source package, or
140 if you want to do development, you also need the following packages:
142 * Flex and Bison are needed to build a CVS checkout or if you changed the
143 actual scanner and parser definition files. If you need them, be sure to
144 get Flex 2.5.4 or later and Bison 1.50 or later. Other yacc programs can
145 sometimes be used, but doing so requires extra effort and is not
146 recommended. Other lex programs will definitely not work.
148 If you need to get a GNU package, you can find it at your local GNU mirror site
149 (see http://www.gnu.org/order/ftp.html for a list) or at ftp://ftp.gnu.org/
151 Also check that you have sufficient disk space. You will need about 65 MB for
152 the source tree during compilation and about 15 MB for the installation
153 directory. An empty database cluster takes about 25 MB, databases take about
154 five times the amount of space that a flat text file with the same data would
155 take. If you are going to run the regression tests you will temporarily need up
156 to an extra 90 MB. Use the "df" command to check for disk space.
158 -------------------------------------------------------------------------------
162 The internal data storage format changes with new releases of PostgreSQL.
163 Therefore, if you are upgrading an existing installation that does not have a
164 version number "7.3.x", you must back up and restore your data as shown here.
165 These instructions assume that your existing installation is under the "/usr/
166 local/pgsql" directory, and that the data area is in "/usr/local/pgsql/data".
167 Substitute your paths appropriately.
169 1. Make sure that your database is not updated during or after the backup.
170 This does not affect the integrity of the backup, but the changed data
171 would of course not be included. If necessary, edit the permissions in
172 the file "/usr/local/pgsql/data/pg_hba.conf" (or equivalent) to disallow
173 access from everyone except you.
175 2. To back up your database installation, type:
177 pg_dumpall > outputfile
179 If you need to preserve OIDs (such as when using them as foreign keys),
180 then use the "-o" option when running "pg_dumpall".
181 "pg_dumpall" does not save large objects. Check the Administrator's Guide
182 if you need to do this.
183 To make the backup, you can use the "pg_dumpall" command from the version
184 you are currently running. For best results, however, try to use the
185 "pg_dumpall" command from PostgreSQL 7.3, since this version contains
186 bug fixes and improvements over older versions. While this advice might
187 seem idiosyncratic since you haven't installed the new version yet, it is
188 advisable to follow it if you plan to install the new version in parallel
189 with the old version. In that case you can complete the installation
190 normally and transfer the data later. This will also decrease the
193 3. If you are installing the new version at the same location as the old one
194 then shut down the old server, at the latest before you install the new
197 kill -INT `cat /usr/local/pgsql/data/postmaster.pid`
199 Versions prior to 7.0 do not have this "postmaster.pid" file. If you are
200 using such a version you must find out the process id of the server
201 yourself, for example by typing "ps ax | grep postmaster", and supply it
202 to the "kill" command.
203 On systems that have PostgreSQL started at boot time, there is probably a
204 start-up file that will accomplish the same thing. For example, on a Red
205 Hat Linux system one might find that
207 /etc/rc.d/init.d/postgresql stop
209 works. Another possibility is "pg_ctl stop".
211 4. If you are installing in the same place as the old version then it is
212 also a good idea to move the old installation out of the way, in case you
213 have trouble and need to revert to it. Use a command like this:
215 mv /usr/local/pgsql /usr/local/pgsql.old
217 After you have installed PostgreSQL 7.3, create a new database directory and
218 start the new server. Remember that you must execute these commands while
219 logged in to the special database user account (which you already have if you
222 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
223 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
225 Finally, restore your data with
227 /usr/local/pgsql/bin/psql -d template1 -f outputfile
229 using the *new* psql.
230 These topics are discussed at length in the Administrator's Guide, which you
231 are encouraged to read in any case.
233 -------------------------------------------------------------------------------
235 Installation Procedure
238 The first step of the installation procedure is to configure the source
239 tree for your system and choose the options you would like. This is done
240 by running the "configure" script. For a default installation simply
245 This script will run a number of tests to guess values for various system
246 dependent variables and detect some quirks of your operating system, and
247 finally will create several files in the build tree to record what it
248 found. (You can also run "configure" in a directory outside the source
249 tree if you want to keep the build directory separate.)
250 The default configuration will build the server and utilities, as well as
251 all client applications and interfaces that require only a C compiler.
252 All files will be installed under "/usr/local/pgsql" by default.
253 You can customize the build and installation process by supplying one or
254 more of the following command line options to "configure":
258 Install all files under the directory "PREFIX" instead of "/usr/
259 local/pgsql". The actual files will be installed into various
260 subdirectories; no files will ever be installed directly into the
262 If you have special needs, you can also customize the individual
263 subdirectories with the following options.
265 --exec-prefix=EXEC-PREFIX
267 You can install architecture-dependent files under a different
268 prefix, "EXEC-PREFIX", than what "PREFIX" was set to. This can be
269 useful to share architecture-independent files between hosts. If
270 you omit this, then "EXEC-PREFIX" is set equal to "PREFIX" and both
271 architecture-dependent and independent files will be installed
272 under the same tree, which is probably what you want.
276 Specifies the directory for executable programs. The default is
277 "EXEC-PREFIX/bin", which normally means "/usr/local/pgsql/bin".
281 Sets the directory for read-only data files used by the installed
282 programs. The default is "PREFIX/share". Note that this has nothing
283 to do with where your database files will be placed.
285 --sysconfdir=DIRECTORY
287 The directory for various configuration files, "PREFIX/etc" by
292 The location to install libraries and dynamically loadable modules.
293 The default is "EXEC-PREFIX/lib".
295 --includedir=DIRECTORY
297 The directory for installing C and C++ header files. The default is
302 Documentation files, except "man" pages, will be installed into
303 this directory. The default is "PREFIX/doc".
307 The man pages that come with PostgreSQL will be installed under
308 this directory, in their respective "manx" subdirectories. The
309 default is "PREFIX/man".
310 Note: Care has been taken to make it possible to install
311 PostgreSQL into shared installation locations (such as "/usr/
312 local/include") without interfering with the namespace of the
313 rest of the system. First, the string "/postgresql" is
314 automatically appended to datadir, sysconfdir, and docdir,
315 unless the fully expanded directory name already contains the
316 string "postgres" or "pgsql". For example, if you choose "/usr/
317 local" as prefix, the documentation will be installed in "/usr/
318 local/doc/postgresql", but if the prefix is "/opt/postgres",
319 then it will be in "/opt/postgres/doc". The public C header
320 files of the client interfaces are installed into includedir
321 and are namespace-clean. The internal header files and the
322 server header files are installed into private directories
323 under includedir. See the Programmer's Guide for information
324 about how to get at the header files for each interface.
325 Finally, a private subdirectory will also be created, if
326 appropriate, under libdir for dynamically loadable modules.
328 --with-includes=DIRECTORIES
330 "DIRECTORIES" is a colon-separated list of directories that will be
331 added to the list the compiler searches for header files. If you
332 have optional packages (such as GNU Readline) installed in a non-
333 standard location, you have to use this option and probably also
334 the corresponding "--with-libraries" option.
335 Example: --with-includes=/opt/gnu/include:/usr/sup/include.
337 --with-libraries=DIRECTORIES
339 "DIRECTORIES" is a colon-separated list of directories to search
340 for libraries. You will probably have to use this option (and the
341 corresponding "--with-includes" option) if you have packages
342 installed in non-standard locations.
343 Example: --with-libraries=/opt/gnu/lib:/usr/sup/lib.
345 --enable-nls[=LANGUAGES]
347 Enables Native Language Support (NLS), that is, the ability to
348 display a program's messages in a language other than English.
349 "LANGUAGES" is a space separated list of codes of the languages
350 that you want supported, for example --enable-nls='de fr'. (The
351 intersection between your list and the set of actually provided
352 translations will be computed automatically.) If you do not specify
353 a list, then all available translations are installed.
354 To use this option, you will need an implementation of the gettext
359 Set "NUMBER" as the default port number for server and clients. The
360 default is 5432. The port can always be changed later on, but if
361 you specify it here then both server and clients will have the same
362 default compiled in, which can be very convenient. Usually the only
363 good reason to select a non-default value is if you intend to run
364 multiple PostgreSQL servers on the same machine.
368 Build the PL/Perl server-side language.
372 Build the Python interface module and the PL/Python server-side
373 language. You need to have root access to be able to install the
374 Python module at its default place ("/usr/lib/pythonx.y").
378 Build components that require Tcl/Tk, which are libpgtcl, pgtclsh,
379 pgtksh, and PL/Tcl. But see below about "--without-tk".
383 If you specify "--with-tcl" and this option, then the program that
384 requires Tk (pgtksh) will be excluded.
386 --with-tclconfig=DIRECTORY, --with-tkconfig=DIRECTORY
388 Tcl/Tk installs the files "tclConfig.sh" and "tkConfig.sh", which
389 contain configuration information needed to build modules
390 interfacing to Tcl or Tk. These files are normally found
391 automatically at their well-known locations, but if you want to use
392 a different version of Tcl or Tk you can specify the directory in
397 Build the JDBC driver and associated Java packages.
399 --with-krb4[=DIRECTORY], --with-krb5[=DIRECTORY]
401 Build with support for Kerberos authentication. You can use either
402 Kerberos version 4 or 5, but not both. The "DIRECTORY" argument
403 specifies the root directory of the Kerberos installation; "/usr/
404 athena" is assumed as default. If the relevant header files and
405 libraries are not under a common parent directory, then you must
406 use the "--with-includes" and "--with-libraries" options in
407 addition to this option. If, on the other hand, the required files
408 are in a location that is searched by default (e.g., "/usr/lib"),
409 then you can leave off the argument.
410 "configure" will check for the required header files and libraries
411 to make sure that your Kerberos installation is sufficient before
414 --with-krb-srvnam=NAME
416 The name of the Kerberos service principal. postgres is the
417 default. There's probably no reason to change this.
419 --with-openssl[=DIRECTORY]
421 Build with support for SSL (encrypted) connections. This requires
422 the OpenSSL package to be installed. The "DIRECTORY" argument
423 specifies the root directory of the OpenSSL installation; the
424 default is "/usr/local/ssl".
425 "configure" will check for the required header files and libraries
426 to make sure that your OpenSSL installation is sufficient before
431 Build with PAM (Pluggable Authentication Modules) support.
435 Prevents the use of the Readline library. This disables command-
436 line editing and history in psql, so it is not recommended.
440 Prevents the use of the Zlib library. This disables compression
441 support in pg_dump. This option is only intended for those rare
442 systems where this library is not available.
446 Compiles all programs and libraries with debugging symbols. This
447 means that you can run the programs through a debugger to analyze
448 problems. This enlarges the size of the installed executables
449 considerably, and on non-GCC compilers it usually also disables
450 compiler optimization, causing slowdowns. However, having the
451 symbols available is extremely helpful for dealing with any
452 problems that may arise. Currently, this option is recommended for
453 production installations only if you use GCC. But you should always
454 have it on if you are doing development work or running a beta
459 Enables assertion checks in the server, which test for many "can't
460 happen" conditions. This is invaluable for code development
461 purposes, but the tests slow things down a little. Also, having the
462 tests turned on won't necessarily enhance the stability of your
463 server! The assertion checks are not categorized for severity, and
464 so what might be a relatively harmless bug will still lead to
465 server restarts if it triggers an assertion failure. Currently,
466 this option is not recommended for production use, but you should
467 have it on for development work or when running a beta version.
471 Enables automatic dependency tracking. With this option, the
472 makefiles are set up so that all affected object files will be
473 rebuilt when any header file is changed. This is useful if you are
474 doing development work, but is just wasted overhead if you intend
475 only to compile once and install. At present, this option will work
478 If you prefer a C compiler different from the one "configure" picks then
479 you can set the environment variable CC to the program of your choice. By
480 default, "configure" will pick "gcc" unless this is inappropriate for the
481 platform. Similarly, you can override the default compiler flags with the
484 You can specify environment variables on the "configure" command line,
487 ./configure CC=/opt/bin/gcc CFLAGS='-O2 -pipe'
490 To start the build, type
494 (Remember to use GNU make.) The build may take anywhere from 5 minutes to
495 half an hour depending on your hardware. The last line displayed should
498 All of PostgreSQL is successfully made. Ready to install.
501 If you want to test the newly built server before you install it, you can
502 run the regression tests at this point. The regression tests are a test
503 suite to verify that PostgreSQL runs on your machine in the way the
504 developers expected it to. Type
508 (This won't work as root; do it as an unprivileged user.) It is possible
509 that some tests fail, due to differences in error message wording or
510 floating point results. The file "src/test/regress/README" and the
511 Administrator's Guide contain detailed information about interpreting the
512 test results. You can repeat this test at any later time by issuing the
515 4. Installing The Files
516 Note: If you are upgrading an existing system and are going to
517 install the new files over the old ones, then you should have
518 backed up your data and shut down the old server by now, as
519 explained in the Section called If You Are Upgrading above.
520 To install PostgreSQL enter
524 This will install files into the directories that were specified in step
525 1. Make sure that you have appropriate permissions to write into that
526 area. Normally you need to do this step as root. Alternatively, you could
527 create the target directories in advance and arrange for appropriate
528 permissions to be granted.
529 You can use gmake install-strip instead of gmake install to strip the
530 executable files and libraries as they are installed. This will save some
531 space. If you built with debugging support, stripping will effectively
532 remove the debugging support, so it should only be done if debugging is
533 no longer needed. install-strip tries to do a reasonable job saving
534 space, but it does not have perfect knowledge of how to strip every
535 unneeded byte from an executable file, so if you want to save all the
536 disk space you possibly can, you will have to do manual work.
537 If you built the Python interfaces and you were not the root user when
538 you executed the above command then that part of the installation
539 probably failed. In that case you should become the root user and then do
541 gmake -C src/interfaces/python install
543 If you do not have superuser access you are on your own: you can still
544 take the required files and place them in other directories where Python
545 can find them, but how to do that is left as an exercise.
546 The standard installation provides only the header files needed for
547 client application development. If you plan to do any server-side program
548 development (such as custom functions or data types written in C), then
549 you may want to install the entire PostgreSQL include tree into your
550 target include directory. To do that, enter
552 gmake install-all-headers
554 This adds a megabyte or two to the installation footprint, and is only
555 useful if you don't plan to keep the whole source tree around for
556 reference. (If you do, you can just use the source's include directory
557 when building server-side software.)
558 Client-only installation: If you want to install only the client
559 applications and interface libraries, then you can use these commands:
561 gmake -C src/bin install
562 gmake -C src/include install
563 gmake -C src/interfaces install
566 Uninstallation: To undo the installation use the command "gmake uninstall".
567 However, this will not remove any created directories.
568 Cleaning: After the installation you can make room by removing the built files
569 from the source tree with the command "gmake clean". This will preserve the
570 files made by the configure program, so that you can rebuild everything with
571 "gmake" later on. To reset the source tree to the state in which it was
572 distributed, use "gmake distclean". If you are going to build for several
573 platforms from the same source tree you must do this and re-configure for each
575 If you perform a build and then discover that your configure options were
576 wrong, or if you change anything that configure investigates (for example,
577 software upgrades), then it's a good idea to do "gmake distclean" before
578 reconfiguring and rebuilding. Without this, your changes in configuration
579 choices may not propagate everywhere they need to.
581 -------------------------------------------------------------------------------
583 Post-Installation Setup
587 On some systems that have shared libraries (which most systems do) you need to
588 tell your system how to find the newly installed shared libraries. The systems
589 on which this is *not* necessary include BSD/OS, FreeBSD, HP-UX, IRIX, Linux,
590 NetBSD, OpenBSD, Tru64 UNIX (formerly Digital UNIX), and Solaris.
591 The method to set the shared library search path varies between platforms, but
592 the most widely usable method is to set the environment variable
593 LD_LIBRARY_PATH like so: In Bourne shells ("sh", "ksh", "bash", "zsh")
595 LD_LIBRARY_PATH=/usr/local/pgsql/lib
596 export LD_LIBRARY_PATH
598 or in "csh" or "tcsh"
600 setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
602 Replace /usr/local/pgsql/lib with whatever you set "--libdir" to in step 1. You
603 should put these commands into a shell start-up file such as "/etc/profile" or
604 "~/.bash_profile". Some good information about the caveats associated with this
605 method can be found at http://www.visi.com/~barr/ldpath.html.
606 On some systems it might be preferable to set the environment variable
607 LD_RUN_PATH *before* building.
608 On Cygwin, put the library directory in the PATH or move the ".dll" files into
609 the "bin/" directory.
610 If in doubt, refer to the manual pages of your system (perhaps "ld.so" or
611 "rld"). If you later on get a message like
613 psql: error in loading shared libraries
614 libpq.so.2.1: cannot open shared object file: No such file or directory
616 then this step was necessary. Simply take care of it then.
617 If you are on BSD/OS, Linux, or SunOS 4 and you have root access you can run
619 /sbin/ldconfig /usr/local/pgsql/lib
621 (or equivalent directory) after installation to enable the run-time linker to
622 find the shared libraries faster. Refer to the manual page of "ldconfig" for
623 more information. On FreeBSD, NetBSD, and OpenBSD the command is
625 /sbin/ldconfig -m /usr/local/pgsql/lib
627 instead. Other systems are not known to have an equivalent command.
629 -------------------------------------------------------------------------------
631 Environment Variables
633 If you installed into "/usr/local/pgsql" or some other location that is not
634 searched for programs by default, you should add "/usr/local/pgsql/bin" (or
635 whatever you set "--bindir" to in step 1) into your PATH. Strictly speaking,
636 this is not necessary, but it will make the use of PostgreSQL much more
638 To do this, add the following to your shell start-up file, such as
639 "~/.bash_profile" (or "/etc/profile", if you want it to affect every user):
641 PATH=/usr/local/pgsql/bin:$PATH
644 If you are using "csh" or "tcsh", then use this command:
646 set path = ( /usr/local/pgsql/bin $path )
648 To enable your system to find the man documentation, you need to add a line
649 like the following to a shell start-up file unless you installed into a
650 location that is searched by default.
652 MANPATH=/usr/local/pgsql/man:$MANPATH
655 The environment variables PGHOST and PGPORT specify to client applications the
656 host and port of the database server, overriding the compiled-in defaults. If
657 you are going to run client applications remotely then it is convenient if
658 every user that plans to use the database sets PGHOST. This is not required,
659 however: the settings can be communicated via command line options to most
662 -------------------------------------------------------------------------------
666 The following is a quick summary of how to get PostgreSQL up and running once
667 installed. The Administrator's Guide contains more information.
669 1. Create a user account for the PostgreSQL server. This is the user the
670 server will run as. For production use you should create a separate,
671 unprivileged account ("postgres" is commonly used). If you do not have
672 root access or just want to play around, your own user account is enough,
673 but running the server as root is a security risk and will not work.
677 2. Create a database installation with the "initdb" command. To run "initdb"
678 you must be logged in to your PostgreSQL server account. It will not work
681 root# mkdir /usr/local/pgsql/data
682 root# chown postgres /usr/local/pgsql/data
684 postgres$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
686 The "-D" option specifies the location where the data will be stored. You
687 can use any path you want, it does not have to be under the installation
688 directory. Just make sure that the server account can write to the
689 directory (or create it, if it doesn't already exist) before starting
690 "initdb", as illustrated here.
692 3. The previous step should have told you how to start up the database
693 server. Do so now. The command should look something like
695 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
697 This will start the server in the foreground. To put the server in the
698 background use something like
700 nohup /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data \
701 </dev/null >>server.log 2>&1 </dev/null &
703 To stop a server running in the background you can type
705 kill `cat /usr/local/pgsql/data/postmaster.pid`
707 In order to allow TCP/IP connections (rather than only Unix domain socket
708 ones) you need to pass the "-i" option to "postmaster".
710 4. Create a database:
718 to connect to that database. At the prompt you can enter SQL commands and
721 -------------------------------------------------------------------------------
725 * The PostgreSQL distribution contains a comprehensive documentation set,
726 which you should read sometime. After installation, the documentation can
727 be accessed by pointing your browser to "/usr/local/pgsql/doc/html/
728 index.html", unless you changed the installation directories.
729 The Tutorial should be your first reading if you are completely new to
730 SQL databases. If you are familiar with database concepts then you want
731 to proceed with the Administrator's Guide, which contains information
732 about how to set up the database server, database users, and
735 * Usually, you will want to modify your computer so that it will
736 automatically start the database server whenever it boots. Some
737 suggestions for this are in the Administrator's Guide.
739 * Run the regression tests against the installed server (using the
740 sequential test method). If you didn't run the tests before installation,
741 you should definitely do it now. This is also explained in the
742 Administrator's Guide.
744 -------------------------------------------------------------------------------
748 PostgreSQL has been verified by the developer community to work on the
749 platforms listed below. A supported platform generally means that PostgreSQL
750 builds and installs according to these instructions and that the regression
752 Note: If you are having problems with the installation on a supported
753 platform, please write to <pgsql-bugs@postgresql.org> or <pgsql-
754 ports@postgresql.org>, not to the people listed here.
755 ________________________________________________________________________________
756 |OS______|Processor__|Version|Reported_________________________|Remarks__________|
757 |AIX |RS6000 |7.3 |2002-11-12, Andreas Zeugswetter |see also doc/ |
758 |________|___________|_______|(<ZeugswetterA@spardat.at>)______|FAQ_AIX__________|
759 |BSD/OS |x86 |7.3 |2002-10-25, Bruce Momjian |4.2 |
760 |________|___________|_______|(<pgman@candle.pha.pa.us>)_______|_________________|
761 |FreeBSD |Alpha |7.3 |2002-11-13, Chris Kings-Lynne | |
762 |________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________|
763 |FreeBSD |x86 |7.3 |2002-10-29, 3.3, Nigel J. Andrews| |
764 | | | |(<nandrews@investsystems.co.uk>),| |
765 | | | |4.7, Larry Rosenman | |
766 | | | |(<ler@lerctr.org>), 5.0, Sean | |
767 | | | |Chittenden | |
768 |________|___________|_______|(<sean@chittenden.org>)__________|_________________|
769 |HP-UX |PA-RISC |7.3 |2002-10-28, 10.20 Tom Lane |gcc and cc; see |
770 | | | |(<tgl@sss.pgh.pa.us>), 11.00, |also doc/FAQ_HPUX|
771 | | | |11.11, 32 & 64 bit, Giles Lean | |
772 |________|___________|_______|(<giles@nemeton.com.au>)_________|_________________|
773 |IRIX |MIPS |7.3 |2002-10-27, Ian Barwick |Irix64 Komma 6.5 |
774 |________|___________|_______|(<barwick@gmx.net>)______________|_________________|
775 |Linux |Alpha |7.3 |2002-10-28, Magnus Naeslund |2.4.19-pre6 |
776 |________|___________|_______|(<mag@fbab.net>)_________________|_________________|
777 |Linux |armv4l |7.2 |2001-12-10, Mark Knox |2.2.x |
778 |________|___________|_______|(<segfault@hardline.org>)________|_________________|
779 |Linux |MIPS |7.2 |2001-11-15, Hisao Shibuya |2.0.x; Cobalt |
780 |________|___________|_______|(<shibuya@alpha.or.jp>)__________|Qube2____________|
781 |Linux |PlayStation|7.2 |2001-12-12, Permaine Cheung |#undef |
782 | |2 | |<pcheung@redhat.com>) |HAS_TEST_AND_SET,|
783 |________|___________|_______|_________________________________|slock_t__________|
784 |Linux |PPC74xx |7.3 |2002-10-26, Tom Lane |bye 2.2.18; Apple|
785 |________|___________|_______|(<tgl@sss.pgh.pa.us>)____________|G3_______________|
786 |Linux |S/390 |7.2 |2001-12-12, Permaine Cheung | |
787 |________|___________|_______|<pcheung@redhat.com>)____________|_________________|
788 |Linux |Sparc |7.3 |2002-10-26, Doug McNaught |3.0 |
789 |________|___________|_______|(<doug@mcnaught.org>)____________|_________________|
790 |Linux |x86 |7.3 |2002-10-26, Alvaro Herrera |2.4 |
791 |________|___________|_______|(<alvherre@dcc.uchile.cl>)_______|_________________|
792 |MacOS X |PPC |7.3 |2002-10-28, 10.1, Tom Lane | |
793 | | | |(<tgl@sss.pgh.pa.us>), 10.2.1, | |
794 | | | |Adam Witney | |
795 |________|___________|_______|(<awitney@sghms.ac.uk>)__________|_________________|
796 |NetBSD |Alpha |7.2 |2001-11-20, Thomas Thai |1.5W |
797 |________|___________|_______|(<tom@minnesota.com>)____________|_________________|
798 |NetBSD |arm32 |7.3 |2002-11-19, Patrick Welche |1.6 |
799 |________|___________|_______|(<prlw1@newn.cam.ac.uk>)_________|_________________|
800 |NetBSD |m68k |7.0 |2000-04-10, Henry B. Hotz |Mac 8xx |
801 |________|___________|_______|(<hotz@jpl.nasa.gov>)____________|_________________|
802 |NetBSD |MIPS |7.2.1 |2002-06-13, Warwick Hunter |1.5.3 |
803 |________|___________|_______|(<whunter@agile.tv>)_____________|_________________|
804 |NetBSD |PPC |7.2 |2001-11-28, Bill Studenmund |1.5 |
805 |________|___________|_______|(<wrstuden@netbsd.org>)__________|_________________|
806 |NetBSD |Sparc |7.2 |2001-12-03, Matthew Green |32- and 64-bit |
807 |________|___________|_______|(<mrg@eterna.com.au>)____________|builds___________|
808 |NetBSD |VAX |7.1 |2001-03-30, Tom I. Helbekkmo |1.5 |
809 |________|___________|_______|(<tih@kpnQwest.no>)______________|_________________|
810 |NetBSD |x86 |7.3 |2002-11-14, Patrick Welche |1.6 |
811 |________|___________|_______|(<prlw1@newn.cam.ac.uk>)_________|_________________|
812 |OpenBSD |Sparc |7.3 |2002-11-17, Christopher Kings- |3.2 |
814 |________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________|
815 |OpenBSD |x86 |7.3 |2002-11-14, 3.1 Magnus Naeslund | |
816 | | | |(<mag@fbab.net>), 3.2 Christopher| |
817 | | | |Kings-Lynne | |
818 |________|___________|_______|(<chriskl@familyhealth.com.au>)__|_________________|
819 |Solaris |Sparc |7.3 |2002-10-28, Andrew Sullivan |Solaris 7 & 8; |
820 | | | |(<andrew@libertyrms.info>) |see also doc/ |
821 |________|___________|_______|_________________________________|FAQ_Solaris______|
822 |Solaris |x86 |7.2 |2001-11-28, Martin Renters |2.8; see also |
823 |________|___________|_______|(<martin@datafax.com>)___________|doc/FAQ_Solaris__|
824 |SunOS 4 |Sparc |7.2 |2001-12-04, Tatsuo Ishii (<t- | |
825 |________|___________|_______|ishii@sra.co.jp>)________________|_________________|
826 |Tru64 |Alpha |7.3 |2002-11-05, Alessio Bragadini | |
827 |UNIX____|___________|_______|(<alessio@albourne.com>)_________|_________________|
828 |UnixWare|x86 |7.3 |2002-11-01, 7.1.3 Larry Rosenman |see also doc/ |
829 | | | |(<ler@lerctr.org>), 7.1.1 and |FAQ_SCO |
830 | | | |7.1.2(8.0.0) Olivier Prenant | |
831 |________|___________|_______|(<ohp@pyrenet.fr>)_______________|_________________|
832 |Windows |x86 |7.3 |2002-10-29, Dave Page |with Cygwin; see |
833 | | | |(<dpage@vale-housing.co.uk>), |doc/FAQ_MSWIN |
834 | | | |Jason Tishler | |
835 |________|___________|_______|(<jason@tishler.net>)____________|_________________|
836 |Windows |x86 |7.3 |2002-11-05, Dave Page |native is client-|
837 | | | |(<dpage@vale-housing.co.uk>) |side only; see |
838 | | | | |Administrator's |
839 |________|___________|_______|_________________________________|Guide____________|
841 Unsupported Platforms: The following platforms are either known not to work, or
842 they used to work in a previous release and we did not receive explicit
843 confirmation of a successful test with version 7.3 at the time this list was
844 compiled. We include these here to let you know that these platforms *could* be
845 supported if given some attention.
846 _____________________________________________________________________________
847 |OS__________|Processor|Version|Reported_______________________|Remarks_______|
848 |BeOS |x86 |7.2 |2001-11-29, Cyril Velter |needs updates |
849 | | | |(<cyril.velter@libertysurf.fr>)|to semaphore |
850 |____________|_________|_______|_______________________________|code__________|
851 |DG/UX |m88k |6.3 |1998-03-01, Brian E Gallew |no recent |
852 |5.4R4.11____|_________|_______|(<geek+@cmu.edu>)______________|reports_______|
853 |MkLinux DR1 |PPC750 |7.0 |2001-04-03, Tatsuo Ishii (<t- |7.1 needs OS |
854 |____________|_________|_______|ishii@sra.co.jp>)______________|update?_______|
855 |NeXTSTEP |x86 |6.x |1998-03-01, David Wetzel |bit rot |
856 |____________|_________|_______|(<dave@turbocat.de>)___________|suspected_____|
857 |QNX 4 RTOS |x86 |7.2 |2001-12-10, Bernd Tegge |needs updates |
858 | | | |(<tegge@repas-aeg.de>) |to semaphore |
859 | | | | |code; see also|
860 |____________|_________|_______|_______________________________|doc/FAQ_QNX4__|
861 |QNX RTOS v6 |x86 |7.2 |2001-11-20, Igor Kovalenko |patches |
862 | | | |(<Igor.Kovalenko@motorola.com>)|available in |
863 | | | | |archives, but |
864 | | | | |too late for |
865 |____________|_________|_______|_______________________________|7.2___________|
866 |SCO |x86 |6.5 |1999-05-25, Andrew Merrill |7.2 should |
867 |OpenServer 5| | |(<andrew@compclass.com>) |work, but no |
868 | | | | |reports; see |
870 |____________|_________|_______|_______________________________|FAQ_SCO_______|
871 |System V R4 |m88k |6.2.1 |1998-03-01, Doug Winterburn |needs new TAS |
872 |____________|_________|_______|(<dlw@seavme.xroads.com>)______|spinlock_code_|
873 |System V R4 |MIPS |6.4 |1998-10-28, Frank Ridderbusch |no recent |
874 |____________|_________|_______|(<ridderbusch.pad@sni.de>)_____|reports_______|
875 |Ultrix |MIPS |7.1 |2001-03-26 |TAS spinlock |
877 |____________|_________|_______|_______________________________|detected______|
878 |Ultrix______|VAX______|6.x____|1998-03-01_____________________|______________|
OSDN Git Service
