1 PostgreSQL Installation Instructions
10 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
11 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 &
12 /usr/local/pgsql/bin/createdb test
13 /usr/local/pgsql/bin/psql test
16 The long version is the rest of this document.
18 ------------------------------------------------------------------------
22 In general, a modern Unix-compatible platform should be able to run
23 PostgreSQL. The platforms that had received explicit testing at the time of
24 release are listed in the section called Supported Platforms below. In the
25 doc subdirectory of the distribution there are several platform-specific FAQ
26 documents you might wish to consult if you are having trouble.
28 The following prerequisites exist for building PostgreSQL:
30 * GNU make is required; other make programs will not work. GNU make is
31 often installed under the name gmake; this document will always refer
32 to it by that name. (On GNU/Linux systems GNU make is the default tool
33 with the name make.) To test for GNU make enter
37 If at all possible you should use version 3.76.1 or later.
39 * You need an ISO/ANSI C compiler. Recent versions of GCC are
40 recommendable, but PostgreSQL is known to build with a wide variety of
41 compilers from different vendors.
45 * The GNU Readline library for comfortable line editing and command
46 history retrieval will automatically be used if found. You might wish
47 to install it before proceeding, but it is not required. (On NetBSD,
48 the libedit library is readline-compatible and is used if libreadline
51 * Flex and Bison are not required when building from a released source
52 package because the output files are pre-generated. You will need these
53 programs only when building from a CVS tree or when the actual scanner
54 and parser definition files were changed. If you need them, be sure to
55 get Flex 2.5.4 or later and Bison 1.28 or later. Other yacc programs
56 can sometimes be used, but doing so requires extra efforts and is not
57 recommended. Other lex programs will definitely not work.
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 If you need to get a GNU package, you can find it at your local GNU mirror
63 site (see http://www.gnu.org/order/ftp.html for a list) or at
64 ftp://ftp.gnu.org/gnu/.
66 Also check that you have sufficient disk space. You will need about 30 MB
67 for the source tree during compilation and about 5 MB for the installation
68 directory. An empty database takes about 1 MB, later it takes about five
69 times the amount of space that a flat text file with the same data would
70 take. If you are going to run the regression tests you will temporarily need
71 an extra 20 MB. Use the df command to check for disk space.
73 ------------------------------------------------------------------------
77 The internal data storage format changes with new releases of PostgreSQL.
78 Therefore, if you are upgrading an existing installation that does not have
79 a version number "7.1.x", you must back up and restore your data as shown
80 here. These instructions assume that your existing installation is under the
81 /usr/local/pgsql directory, and that the data area is in
82 /usr/local/pgsql/data. Substitute your paths appropriately.
84 1. Make sure that your database is not updated during or after the backup.
85 This does not affect the integrity of the backup, but the changed data
86 would of course not be included. If necessary, edit the permissions in
87 the file /usr/local/pgsql/data/pg_hba.conf (or equivalent) to disallow
88 access from everyone except you.
90 2. To dump your database installation, type:
92 pg_dumpall > outputfile
94 If you need to preserve the OIDs (such as when using them as foreign
95 keys), then use the -o option when running pg_dumpall. pg_dumpall does
96 not save large objects. Check the Administrator's Guide if you need to
99 Make sure that you use the pg_dumpall command from the version you are
100 currently running. 7.1's pg_dumpall should not be used on older
103 3. If you are installing the new version at the same location as the old
104 one then shut down the old server, at the latest before you install the
107 kill -INT `cat /usr/local/pgsql/data/postmaster.pid`
109 Versions prior to 7.0 do not have this postmaster.pid file. If you are
110 using such a version you must find out the process id of the server
111 yourself, for example by typing ps ax | grep postmaster, and supply it
114 On systems that have PostgreSQL started at boot time, there is probably
115 a start-up file that will accomplish the same thing. For example, on a
116 Red Hat Linux system one might find that
118 /etc/rc.d/init.d/postgresql stop
122 4. If you are installing in the same place as the old version then it is
123 also a good idea to move the old installation out of the way, in case
124 you still need it later on. Use a command like this:
126 mv /usr/local/pgsql /usr/local/pgsql.old
128 After you have installed PostgreSQL 7.1, create a new database directory and
129 start the new server. Remember that you must execute these commands while
130 logged in to the special database user account (which you already have if
133 /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
134 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
136 Finally, restore your data with
138 /usr/local/pgsql/bin/psql -d template1 -f outputfile
142 You can also install the new version in parallel with the old one to
143 decrease the downtime. These topics are discussed at length in the
144 Administrator's Guide, which you are encouraged to read in any case.
146 ------------------------------------------------------------------------
148 Installation Procedure
152 The first step of the installation procedure is to configure the source
153 tree for your system and choose the options you would like. This is
154 done by running the configure script. For a default installation simply
159 This script will run a number of tests to guess values for various
160 system dependent variables and detect some quirks of your operating
161 system, and finally creates several files in the build tree to record
164 The default configuration will build the server and utilities, as well
165 as all client applications and interfaces that only require a C
166 compiler. All files will be installed under /usr/local/pgsql by
169 You can customize the build and installation process by supplying one
170 or more of the following command line options to configure:
174 Install all files under the directory PREFIX instead of
175 /usr/local/pgsql. The actual files will be installed into various
176 subdirectories; no files will ever be installed directly into the
179 If you have special needs, you can also customize the individual
180 subdirectories with the following options.
182 --exec-prefix=EXEC-PREFIX
184 You can install architecture-dependent files under a different
185 prefix, EXEC-PREFIX, than what PREFIX was set to. This can be
186 useful to share architecture-independent files between hosts. If
187 you omit this, then EXEC-PREFIX is set equal to PREFIX and both
188 architecture dependent and independent files will be installed
189 under the same tree, which is probably what you want.
193 Specifies the directory for executable programs. The default is
194 EXEC-PREFIX/bin, which normally means /usr/local/pgsql/bin.
198 Sets the directory for read-only data files used by the installed
199 programs. The default is PREFIX/share. Note that this has nothing
200 to do with where your database files will be placed.
202 --sysconfdir=DIRECTORY
204 The directory for various configuration files, PREFIX/etc by
209 The location to install libraries and dynamically loadable
210 modules. The default is EXEC-PREFIX/lib.
212 --includedir=DIRECTORY
214 The directory for installing C and C++ header files. The default
219 Documentation files, except "man" pages, will be installed into
220 this directory. The default is PREFIX/doc.
224 The man pages that come with PostgreSQL will be installed under
225 this directory, in their respective manx subdirectories. The
226 default is PREFIX/man.
228 Note: To reduce the pollution of shared installation
229 locations (such as /usr/local/include), the string
230 "/postgresql" is automatically appended to datadir,
231 sysconfdir, includedir, and docdir, unless the fully expanded
232 directory name already contains the string "postgres" or
233 "pgsql". For example, if you choose /usr/local as prefix, the
234 C header files will be installed in
235 /usr/local/include/postgresql, but if the prefix is
236 /opt/postgres, then they will be in /opt/postgres/include.
238 --with-includes=DIRECTORIES
240 DIRECTORIES is a colon-separated list of directories that will be
241 added to the list the compiler searches for header files. If you
242 have optional packages (such as GNU Readline) installed in a
243 non-standard location you have to use this option and probably the
244 corresponding --with-libraries option.
246 Example: --with-includes=/opt/gnu/include:/usr/sup/include.
248 --with-libraries=DIRECTORIES
250 DIRECTORIES is a colon-separated list of directories to search for
251 libraries. You will probably have to use this option (and the
252 corresponding --with-includes option) if you have packages
253 installed in non-standard locations.
255 Example: --with-libraries=/opt/gnu/lib:/usr/sup/lib.
259 Enables locale support. There is a performance penalty associated
260 with locale support, but if you are not in an English-speaking
261 environment you will most likely need this.
265 Enables single-byte character set recode support. See the
266 Administrator's Guide about this feature.
270 Allows the use of multibyte character encodings. This is primarily
271 for languages like Japanese, Korean, and Chinese. Read the
272 Administrator's Guide for details.
276 Set NUMBER as the default port number for server and clients. The
277 default is 5432. The port can always be changed later on, but if
278 you specify it here then both server and clients will have the
279 same default compiled in, which can be very convenient.
283 Build the C++ interface library.
287 Build the Perl interface module. The Perl interface will be
288 installed at the usual place for Perl modules (typically under
289 /usr/lib/perl), so you must have root access to perform the
290 installation step (see step 4). You need to have Perl 5 installed
295 Build the Python interface module. You need to have root access to
296 be able to install the Python module at its default place
297 (/usr/lib/pythonx.y). To be able to use this option, you must have
298 Python installed and your system needs to support shared
299 libraries. If you instead want to build a new complete interpreter
300 binary, you will have to do it manually.
304 Builds components that require Tcl/Tk, which are libpgtcl,
305 pgtclsh, pgtksh, pgaccess, and PL/Tcl. But see below about
310 If you specify --with-tcl and this option, then programs that
311 require Tk (i.e., pgtksh and pgaccess) will be excluded.
313 --with-tclconfig=DIRECTORY, --with-tkconfig=DIRECTORY
315 Tcl/Tk installs the files tclConfig.sh and tkConfig.sh which
316 contain certain configuration information that is needed to build
317 modules interfacing to Tcl or Tk. These files are normally found
318 automatically at their well-known location, but if you want to use
319 a different version of Tcl or Tk you can specify the directory
324 Build the ODBC driver package.
326 --with-odbcinst=DIRECTORY
328 Specifies the directory where the ODBC driver will expect its
329 odbcinst.ini configuration file. The default is
330 /usr/local/pgsql/etc or whatever you specified as --sysconfdir. A
331 default file will be installed there. If you intend to share the
332 odbcinst.ini file between several ODBC drivers then you may want
335 --with-krb4=DIRECTORY, --with-krb5=DIRECTORY
337 Build with support for Kerberos authentication. You can use either
338 Kerberos version 4 or 5, but not both. The DIRECTORY argument
339 specifies the root directory of the Kerberos installation;
340 /usr/athena is assumed as default. If the relevant headers files
341 and libraries are not under a common parent directory, then you
342 must use the --with-includes and --with-libraries options in
343 addition to this option. If, on the other hand, the required files
344 are in a location that is searched by default (e.g., /usr/lib),
345 then you can leave off the argument.
347 configure will check for the required header files and libraries
348 to make sure that your Kerberos installation is sufficient before
351 --with-krb-srvnam=NAME
353 The name of the Kerberos service principal. "postgres" is the
354 default. There's probably no reason to change this.
356 --with-openssl=DIRECTORY
358 Build with support for SSL (encrypted) connections. This requires
359 the OpenSSL package to be installed. The DIRECTORY argument
360 specifies the root directory of the OpenSSL installation; the
361 default is /usr/local/ssl.
363 configure will check for the required header files and libraries
364 to make sure that your OpenSSL installation is sufficient before
369 Build the JDBC driver and associated Java packages. This option
370 requires Ant to be installed (as well as a JDK, of course). Refer
371 to the JDBC driver documentation in the Programmer's Guide for
376 Enables the PostgreSQL server to use the syslog logging facility.
377 (Using this option does not mean that you must log with syslog or
378 even that it will be done by default, it simply makes it possible
379 to turn this option on at run time.)
383 Compiles all programs and libraries with debugging symbols. This
384 means that you can run the programs through a debugger to analyze
385 problems. This enlarges the size of the installed executables
386 considerably, and on non-gcc compilers it usually also disables
387 compiler optimization, causing slowdowns. However, having the
388 symbols available is extremely helpful for dealing with any
389 problems that may arise. Currently, this option is considered of
390 marginal value for production installations, but you should have
391 it on if you are doing development work or running a beta version.
395 Enables assertion checks in the server, which test for many "can't
396 happen" conditions. This is invaluable for code development
397 purposes, but the tests slow things down a little. Also, having
398 the tests turned on won't necessarily enhance the stability of
399 your server! The assertion checks are not categorized for
400 severity, and so what might be a relatively harmless bug will
401 still lead to postmaster restarts if it triggers an assertion
402 failure. Currently, this option is not recommended for production
403 use, but you should have it on for development work or when
404 running a beta version.
406 If you prefer a C or C++ compiler different from the one configure
407 picks then you can set the environment variables CC and CXX,
408 respectively, to the program of your choice. Similarly, you can
409 override the default compiler flags with the CFLAGS and CXXFLAGS
410 variables. For example:
412 env CC=/opt/bin/gcc CFLAGS='-02 -pipe' ./configure
416 To start the build, type
420 (Remember to use GNU make.) The build can take anywhere from 5 minutes
421 to half an hour. The last line displayed should be
423 All of PostgreSQL is successfully made. Ready to install.
427 If you want to test the newly built server before you install it, you
428 can run the regression tests at this point. The regression tests are a
429 test suite to verify that PostgreSQL runs on your machine in the way
430 the developers expected it to. Type
434 It is possible that some tests fail, due to differences in error
435 message wording or floating point results. The file
436 src/test/regress/README and the Administrator's Guide contain detailed
437 information about interpreting the test results. You can repeat this
438 test at any later time by issuing the same command.
440 4. Installing The Files
442 Note: If you are upgrading an existing system and are going
443 to install the new files over the old ones then you should
444 have backed up your data and shut down the old server by now,
445 as explained in the section called If You Are Upgrading
448 To install PostgreSQL enter
452 This will install files into the directories that were specified in
453 step 1. Make sure that you have appropriate permissions to write into
454 that area. Normally you need to do this step as root. Alternatively,
455 you could create the target directories in advance and arrange for
456 appropriate permissions to be granted.
458 If you built the Perl or Python interfaces and you were not the root
459 user when you executed the above command then that part of the
460 installation probably failed. In that case you should become the root
463 gmake -C src/interfaces/perl5 install
464 gmake -C src/interfaces/python install
466 Due to a quirk in the Perl build environment the first command will
467 actually rebuild the complete interface and then install it. This is
468 not harmful, just unusual. If you do not have superuser access you are
469 on your own: you can still take the required files and place them in
470 other directories where Perl or Python can find them, but how to do
471 that is left as an exercise.
473 The standard install installs only the header files needed for client
474 application development. If you plan to do any server-side program
475 development (such as custom functions or datatypes written in C), then
476 you may want to install the entire PostgreSQL include tree into your
477 target include directory. To do that, enter
479 gmake install-all-headers
481 This adds a megabyte or two to the install footprint, and is only
482 useful if you don't plan to keep the whole source tree around for
483 reference. (If you do, you can just use the source's include directory
484 when building server-side software.)
486 Client-only installation. If you want to install only the client
487 applications and interface libraries, then you can use these commands:
489 gmake -C src/bin install
490 gmake -C src/interfaces install
493 To undo the installation use the command gmake uninstall. However, this
494 will not remove the Perl and Python interfaces and it will not remove
497 After the installation you can make room by removing the built files from
498 the source tree with the gmake clean command. This will preserve the choices
499 made by the configure program, so that you can rebuild everything with gmake
500 later on. To reset the source tree to the state in which it was distributed,
501 use gmake distclean. If you are going to build for several platforms from
502 the same source tree you must do this and re-configure for each build.
504 ------------------------------------------------------------------------
506 Post-Installation Setup
510 On some systems that have shared libraries (which most systems do) you need
511 to tell your system how to find the newly installed shared libraries. The
512 systems on which this is not necessary include FreeBSD, HP/UX, Irix, Linux,
513 NetBSD, OpenBSD, OSF/1 (Digital Unix, Tru64 UNIX), and Solaris.
515 The method to set the shared library search path varies between platforms,
516 but the most widely usable method is to set the environment variable
517 LD_LIBRARY_PATH like so: In Bourne shells (sh, ksh, bash, zsh)
519 LD_LIBRARY_PATH=/usr/local/pgsql/lib
520 export LD_LIBRARY_PATH
524 setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
526 Replace /usr/local/pgsql/lib with whatever you set --libdir to in step 1.
527 You should put these commands into a shell start-up file such as
528 /etc/profile or ~/.bash_profile. Some good information about the caveats
529 associated with the method can be found at
530 http://www.visi.com/~barr/ldpath.html.
532 On some systems it might be preferable to set the environment variable
533 LD_RUN_PATH before building.
535 If in doubt, refer to the manual pages of your system (perhaps ld.so or
536 rld). If you later on get a message like
538 psql: error in loading shared libraries
539 libpq.so.2.1: cannot open shared object file: No such file or directory
541 then this step was necessary. Simply take care of it then.
543 ------------------------------------------------------------------------
545 Environment Variables
547 If you installed into /usr/local/pgsql or some other location that is not
548 searched for programs by default, you need to add /usr/local/pgsql/bin (or
549 what you set --bindir to in step 1) into your PATH. To do this, add the
550 following to your shell start-up file, such as ~/.bash_profile (or
551 /etc/profile, if you want it to affect every user):
553 PATH=$PATH:/usr/local/pgsql/bin
555 If you are using csh or tcsh, then use this command:
557 set path = ( /usr/local/pgsql/bin path )
559 To enable your system to find the man documentation, you need to add a line
560 like the following to a shell start-up file:
562 MANPATH=$MANPATH:/usr/local/pgsql/man
564 The environment variables PGHOST and PGPORT specify to client applications
565 the host and port of the database server, overriding the compiled-in
566 defaults. If you are going to run client applications remotely then it is
567 convenient if every user that plans to use the database sets PGHOST, but it
568 is not required and the settings can be communicated via command line
569 options to most client programs.
571 ------------------------------------------------------------------------
575 The following is a quick summary of how to get PostgreSQL up and running
576 once installed. The Administrator's Guide contains more information.
578 1. Create a user account for the PostgreSQL server. This is the user the
579 server will run as. For production use you should create a separate,
580 unprivileged account ("postgres" is commonly used). If you do not have
581 root access or just want to play around, your own user account is
582 enough, but running the server as root is a security risk and will not
587 2. Create a database installation with the initdb command. To run initdb
588 you must be logged in to your PostgreSQL server account. It will not
591 root# mkdir /usr/local/pgsql/data
592 root# chown postgres /usr/local/pgsql/data
594 postgres$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
596 The -D option specifies the location where the data will be stored. You
597 can use any path you want, it does not have to be under the
598 installation directory. Just make sure that the server account can
599 write to the directory (or create it, if it doesn't already exist)
600 before starting initdb, as illustrated here.
602 3. The previous step should have told you how to start up the database
603 server. Do so now. The command should look something like
605 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
607 This will start the server in the foreground. To put the server in the
608 background use something like
610 nohup /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data \
611 </dev/null >>server.log 2>&1 </dev/null &
613 To stop a server running in the background you can type
615 kill `cat /usr/local/pgsql/data/postmaster.pid`
617 In order to allow TCP/IP connections (rather than only Unix domain
618 socket ones) you need to pass the -i option to postmaster.
620 4. Create a database:
628 to connect to that database. At the prompt you can enter SQL commands
629 and start experimenting.
631 ------------------------------------------------------------------------
635 * The Tutorial should be your first reading if you are completely new to
636 SQL databases. It should have been installed at
637 /usr/local/pgsql/doc/html/tutorial.html unless you changed the
638 installation directories.
640 * If you are familiar with database concepts then you want to proceed
641 with the Administrator's Guide, which contains information about how to
642 set up the database server, database users, and authentication. It can
643 be found at /usr/local/pgsql/doc/html/admin.html.
645 * Usually, you will want to modify your computer so that it will
646 automatically start the database server whenever it boots. Some
647 suggestions for this are in the Administrator's Guide.
649 * Run the regression tests against the installed server (using the
650 sequential test method). If you didn't run the tests before
651 installation, you should definitely do it now. This is also explained
652 in the Administrator's Guide.
654 ------------------------------------------------------------------------
658 PostgreSQL has been verified by the developer community to work on the
659 platforms listed below. A supported platform generally means that PostgreSQL
660 builds and installs according to these instructions and that the regression
663 Note: If you are having problems with the installation on a
664 supported platform, please write to <pgsql-bugs@postgresql.org> or
665 <pgsql-ports@postgresql.org>, not to the people listed here.
667 OS Processor Version Reported Remarks
668 AIX 4.3.3RS6000 7.1 2001-03-21, Gilles Darold see also
669 (<gilles@darold.net>) doc/FAQ_AIX
670 BeOS x86 7.1 2001-02-26, Cyril Velter requires new
671 5.0.4 (<cyril.velter@libertysurf.fr>) BONE networking
673 BSD/OS x86 7.1 2001-03-20, Bruce Momjian
674 4.01 (<pgman@candle.pha.pa.us>)
675 Compaq Alpha 7.1 2001-03-26, Adriaan Joubert 4.0-5.0, cc and
676 Tru64 (<a.joubert@albourne.com>) gcc
678 FreeBSD x86 7.1 2001-03-19, Vince Vielhaber
680 HP/UX PA-RISC 7.1 2001-03-19, 10.20 Tom Lane 32- and 64-bit
681 (<tgl@sss.pgh.pa.us>), 2001-03-22, on 11.00; see
682 11.00, 11i Giles Lean also
683 (<giles@nemeton.com.au>) doc/FAQ_HPUX
684 IRIX MIPS 7.1 2001-03-22, Robert Bruccoleri 32-bit
685 6.5.11 (<bruc@acm.org>) compilation
687 Linux Alpha 7.1 2001-01-23, Ryan Kirkpatrick
688 2.2.x (<pgsql@rkirkpat.net>)
689 Linux armv4l 7.1 2001-02-22, Mark Knox
690 2.2.x (<segfault@hardline.org>)
691 Linux MIPS 7.1 2001-03-30, Dominic Eidson Cobalt Qube
692 2.0.x (<sauron@the-infinite.org>)
693 Linux PPC74xx 7.1 2001-03-19, Tom Lane Apple G3
694 2.2.18 (<tgl@sss.pgh.pa.us>)
695 Linux S/390 7.1 2000-11-17, Neale Ferguson
696 (<Neale.Ferguson@softwareAG-usa.com>)
697 Linux Sparc 7.1 2001-01-30, Ryan Kirkpatrick
698 2.2.15 (<pgsql@rkirkpat.net>)
699 Linux x86 7.1 2001-03-19, Thomas Lockhart 2.0.x, 2.2.x,
700 (<thomas@fourpalms.org>) 2.4.2
701 MacOS X PPC 7.1 2000-12-11, Peter Bierman Darwin (only)
702 (<bierman@apple.com>), 2000-12-11, Beta-2 or higher
703 Daniel Luke (<dluke@geeklair.net>)
704 NetBSD Alpha 7.1 2001-03-22, Giles Lean
705 1.5 (<giles@nemeton.com.au>)
706 NetBSD arm32 7.1 2001-03-21, Patrick Welche
707 1.5E (<prlw1@cam.ac.uk>)
708 NetBSD m68k 7.0 2000-04-10, Henry B. Hotz Mac 8xx
709 (<hotz@jpl.nasa.gov>)
710 NetBSD PPC 7.1 2001-04-05, Henry B. Hotz Mac G4
711 (<hotz@jpl.nasa.gov>)
712 NetBSD Sparc 7.1 2000-04-05, Matthew Green 32- and 64-bit
713 (<mrg@eterna.com.au>) builds
714 NetBSD VAX 7.1 2001-03-30, Tom I. Helbekkmo
715 1.5 (<tih@kpnQwest.no>)
716 NetBSD x86 7.1 2001-03-23, Giles Lean
717 1.5 (<giles@nemeton.com.au>)
718 OpenBSD Sparc 7.1 2001-03-23, Brandon Palmer
719 2.8 (<bpalmer@crimelabs.net>)
720 OpenBSD x86 7.1 2001-03-21, Brandon Palmer
721 2.8 (<bpalmer@crimelabs.net>)
722 SCO x86 7.1 2001-03-19, Larry Rosenman UDK FS compiler;
723 UnixWare (<ler@lerctr.org>) see also
725 Solaris Sparc 7.1 2001-03-22, Marc Fournier see also
726 2.7-8 (<scrappy@hub.org>), 2001-03-25, doc/FAQ_Solaris
727 Justin Clift (<justin@postgresql.org>)
728 Solaris x86 7.1 2001-03-27, Mathijs Brands see also
729 2.8 (<mathijs@ilse.nl>) doc/FAQ_Solaris
730 SunOS Sparc 7.1 2001-03-23, Tatsuo Ishii
731 4.1.4 (<t-ishii@sra.co.jp>)
732 Windows x86 7.1 2001-03-16, Jason Tishler with Cygwin
733 NT/2000 (<Jason.Tishler@dothill.com>) toolset, see
737 Unsupported Platforms. The following platforms have not been verified to
738 work. Platforms listed for version 6.3.x and later should also work with
739 7.1, but we did not receive explicit confirmation of such at the time this
740 list was compiled. We include these here to let you know that these
741 platforms could be supported if given some attention.
743 OS Processor VersionReported Remarks
744 DGUX m88k 6.3 1998-03-01, Brian E Gallew 6.4 probably OK
745 5.4R4.11 (<geek+@cmu.edu>)
746 MkLinux DR1 PPC750 7.0 2001-04-03, Tatsuo Ishii 7.1 needs OS
747 (<t-ishii@sra.co.jp>) update?
748 NextStep x86 6.x 1998-03-01, David Wetzel bit rot
749 (<dave@turbocat.de>) suspected
750 QNX 4.25 x86 7.0 2000-04-01, Dr. Andreas Spinlock code
751 Kardos needs work. See
752 (<kardos@repas-aeg.de>) also
754 SCO x86 6.5 1999-05-25, Andrew Merrill 7.1 should work,
755 OpenServer (<andrew@compclass.com>) but no reports;
758 System V R4 m88k 6.2.1 1998-03-01, Doug Winterburn needs new TAS
759 (<dlw@seavme.xroads.com>) spinlock code
760 System V R4 MIPS 6.4 1998-10-28, Frank no 64-bit
762 (<ridderbusch.pad@sni.de>)
763 Ultrix MIPS 7.1 2001-03-26 TAS spinlock
766 Ultrix VAX 6.x 1998-03-01 No recent
769 Windows 9x, x86 7.1 2001-03-26, Magnus Hagander client-side
770 ME, NT, (<mha@sollentuna.net>) libraries (libpq
772 (native) ODBC/JDBC, no