-The source path is /usr/src/pgsql (other paths are possible).
+The source path is /usr/src/pgsql (other paths are possible).
-The runtime path is /usr/local/pgsql (other paths are possible).
+The runtime path is /usr/local/pgsql (other paths are possible).
Commands were tested on RedHat Linux version 4.2 using the tcsh shell.
Except where noted, they will probably work on most systems. Commands
-like ps and tar vary wildly on what options you should use on each
-platform. Use common sense before typing in these commands.
+like ps and tar may vary wildly
+between platforms on what options you should use.
+Use common sense before typing in these commands.
gmake
in this document). They will not
work with non-GNU
make programs. If you
have GNU
make installed under the name
-make
instead of gmake
, that's OK, but
-you need to have it.
+make
instead of gmake
, then you will use the
+command make instead. That's OK, but
+you need to have the GNU form of
make to succeed with
+an installation.
Requirements to Run <ProductName>Postgres</ProductName>
-Information on supported platforms is in another chapter. In general, most Unix-compatible
+Up to date information on supported platforms is at
+http://www.postgresql.org/docs/admin/install.htm.
+
+ In general, most Unix-compatible
platforms with modern libraries should be able to run
Postgres.
-Create account postgres if it does not already exist.
+Create the
Postgres superuser account
+(postgres is commonly used) if it does not already exist.
-Log into account postgres.
+Log in
to the Postgres superuser account.
Check that you have sufficient disk space. You will need about
- 17 Mbytes for /usr/src/pgsql, about 2 Mbytes for /usr/local/pgsql
+ 17 Mbytes for /usr/src/pgsql,
+about 2 Mbytes for /usr/local/pgsql
(excluding your database) and 1 Mbyte for an empty database.
The database will temporarily grow to about 20 Mbytes during the
regression tests. You will also need about 3 Mbytes for the
We therefore recommend that during installation and testing you
- have well over 20 Mbytes free under /usr/local and another 25 Mbytes
+ have well over 20 Mbytes free under /usr/local and another 25 Mbytes
free on the disk partition containing your database. Once you
delete the source files, tar file and regression database, you
- will need 2 Mbytes for /usr/local/pgsql, 1 Mbyte for the empty
+ will need 2 Mbytes for /usr/local/pgsql, 1 Mbyte for the empty
database, plus about five times the space you would require to
store your database data in a flat file.
- To check for disk space, use df -k.
+ To check for disk space, use
+$ df -k
+
+
-Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.4.tar.gz from the
- Internet. Store it in your home directory.
+Ftp file
+
ftp://ftp.postgresql.org/pub/postgresql-v6.4.tar.gz+ from the Internet. Store it in your home directory.
-Some platforms use flex. If your system uses flex then make sure
- you have a good version. To check, type flex --version.
+Some platforms use
flex.
+If your system uses
flex then make sure
+ you have a good version. To check, type
+$ flex --version
+
+
- If the flex command is not found then you probably do not need it.
+ If the
flex command is not found then you probably do not need it.
If the version is 2.5.2 or 2.5.4 or greater then you are okay. If it
- is 2.5.3 or before 2.5.2 then you will have to upgrade flex. You may
- get it at ftp://prep.ai.mit.edu/pub/gnu/flex-2.5.4.tar.gz.
+ is 2.5.3 or before 2.5.2 then you will have to upgrade
flex. You may
+ get it at
+
ftp://prep.ai.mit.edu/pub/gnu/flex-2.5.4.tar.gz.
- If you need flex and don't have it or have the wrong version, then
+ If you need
flex and don't have it or have the wrong version, then
you will be told so when you attempt to compile the program. Feel
free to skip this step if you aren't sure you need it. If you do
- need it then you will be told to install/upgrade flex when you try to
- compile.
+ need it then you will be told to install/upgrade
flex when you try to
- To install it, type the following:
+You may want to do the entire
flex installation from
+the root account, though that is not absolutely necessary.
+Assuming that you want the installation to place files in the usual default
+areas, type the following:
- cd
- gunzip -c flex-2.5.4.tar.gz | tar xvf -
- cd flex-2.5.4
- configure --prefix=/usr
- make
- make check
- # You must be root when typing the next line.
- make install
- cd
- rm -rf flex-2.5.4
+$ su -
+$ cd /usr/local/src
+ftp prep.ai.mit.edu
+ftp> cd /pub/gnu/
+ftp> binary
+ftp> get flex-2.5.4.tar.gz
+ftp> quit
+$ gunzip -c flex-2.5.4.tar.gz | tar xvf -
+$ cd flex-2.5.4
+$ configure --prefix=/usr
+$ gmake
+$ gmake check
+# You must be root when typing the next line:
+$ gmake install
+$ cd /usr/local/src
+$ rm -rf flex-2.5.4
- This will update files /usr/man/man1/flex.1, /usr/bin/flex,
- /usr/lib/libfl.a, /usr/include/FlexLexer.h and will add link
- /usr/bin/flex++ which points to flex.
+ This will update files /usr/man/man1/flex.1,
+ /usr/bin/flex,
+ /usr/lib/libfl.a,
+ /usr/include/FlexLexer.h and will add a link
+ /usr/bin/flex++ which points to flex.
If you are upgrading an existing system then back up your database.
For alpha- and beta-level releases, the database format is liable
- to change often every few weeks with no notice besides a quick comment
+ to change, often every few weeks, with no notice besides a quick comment
in the HACKERS mailing list. Full releases always require a dump/reload
from previous releases. It is therefore a bad idea to skip this
- step. Also, do not use the pg_dumpall script from v6.0 or everything
+ step.
+
+
+Do not use the
pg_dumpall +script from v6.0 or everything
will be owned by the
Postgres super user.
- Type (with the gunzip line
- and the following line typed as one line):
+
+
+To use the latest
pg_dumpall script on your
+existing database before upgrading
Postgres, type:
- cd
- gunzip -c postgresql-v6.4.tar.gz |
- tar xvf - src/bin/pg_dump/pg_dumpall
- chmod a+x src/bin/pg_dump/pg_dumpall
- src/bin/pg_dump/pg_dumpall > db.out
- rm -rf src
+$ cd
+$ gunzip -c postgresql-v6.4.tar.gz \
+ | tar xvf - src/bin/pg_dump/pg_dumpall
+$ chmod a+x src/bin/pg_dump/pg_dumpall
+$ src/bin/pg_dump/pg_dumpall > db.out
+$ rm -rf src
If you wish to preserve object id's (oids), then use the -o
- option when running pg_dumpall. However, unless you have a
- special reason for doing this, don't do it.
+ option when running
pg_dumpall. However, unless you have a
+ special reason for doing this (such as using OIDs as keys
+in tables), don't do it.
- If the pg_dumpall command seems to take a long time and you think
- it might have died, then, from another terminal, use "ls -l db.out"
+ If the
pg_dumpall command seems to take a long time and you think
+ it might have died, then, from another terminal, type
+$ ls -l db.out
+
several times to see if the size of the file is growing.
Please note that if you are upgrading from a version prior to
Postgres95 v1.09 then you must back up your database, install
Postgres95 v1.09, restore your database, then back it up again.
- You should also read files /usr/src/pgsql/migration/*.
+ You should also read the release notes which should cover any release-specific issues.
+
You must make sure that your database is not updated in the middle of
your backup. If necessary, bring down postmaster, edit the permissions
- in file /usr/local/pgsql/data/pg_hba.conf to allow only you on, then
- bring postmaster back up.
+ in file /usr/local/pgsql/data/pg_hba.conf to allow only you on, then
+ bring
postmaster back up.
+
+
If you are upgrading an existing system then kill the postmaster. Type
- ps -ax | grep postmaster
+$ ps -ax | grep postmaster
+
This should list the process numbers for a number of processes. Type
- the following line, with "???" replaced by the process id for process
- "postmaster". (Do not use the id for process "grep postmaster".) Type
- kill ???
- with "???" modified as indicated.
+ the following line, with pid
+ replaced by the process id for process
+ postmaster.
+(Do not use the id for process "grep postmaster".) Type
+$ kill pid
+
+to actually stop the process.
+
+
+On systems which have
Postgres started at boot time, there
+is probably a startup file which will accomplish the same thing. For example, on my
+Linux system I can type
+$ /etc/rc.d/init.d/postgres.init stop
+
+
If you are upgrading an existing system then move the old directories
out of the way. If you are short of disk space then you may have to
back up and delete the directories instead. If you do this, save the
- old database in the /usr/local/pgsql/data directory tree. At a
- minimum, save file /usr/local/pgsql/data/pg_hba.conf.
+ old database in the /usr/local/pgsql/data directory tree. At a
+ minimum, save file /usr/local/pgsql/data/pg_hba.conf.
Type the following:
- su
- cd /usr/src
- mv pgsql pgsql_6_0
- cd /usr/local
- mv pgsql pgsql_6_0
- exit
+$ su -
+$ cd /usr/src
+$ mv pgsql pgsql_6_0
+$ cd /usr/local
+$ mv pgsql pgsql_6_0
+$ exit
+
- If you are not using /usr/local/pgsql/data as your data directory
+ If you are not using /usr/local/pgsql/data
+ as your data directory
(check to see if environment variable PGDATA is set to something
else) then you will also want to move this directory in the same
manner.
Make new source and install directories. The actual paths can be
- different for your installation; be consistant throughout this procedure.
+ different for your installation but you must be consistant throughout this procedure.
+
+There are two places in this installation procedure where you will have an opportunity
+to specify installation locations for programs, libraries, documentation, and other files.
+Usually it is sufficient to specify these at the make install stage
+of installation.
+
+
Type
- su
- cd /usr/src
- mkdir pgsql
- chown postgres:postgres pgsql
- cd /usr/local
- mkdir pgsql
- chown postgres:postgres pgsql
- exit
+$ su
+$ cd /usr/src
+$ mkdir pgsql
+$ chown postgres:postgres pgsql
+$ cd /usr/local
+$ mkdir pgsql
+$ chown postgres:postgres pgsql
+$ exit
Unzip and untar the new source file. Type
- cd /usr/src/pgsql
- gunzip -c ~/postgresql-v6.4.tar.gz | tar xvf -
+$ cd /usr/src/pgsql
+$ gunzip -c ~/postgresql-v6.4.tar.gz | tar xvf -
you can specify your actual installation path for
the build process (see the --prefix option below). Type
- cd /usr/src/pgsql/src
- ./configure [ options as described below ]
+$ cd /usr/src/pgsql/src
+$ ./configure [ options as described below ]
"template" file from the files provided in the template subdirectory.
If it cannot guess which one to use for your system, it will say so and
exit. In that case you'll need to figure out which one to use and run
- configure again, this time giving the --with-template=TEMPLATE option to
- make the right file be chosen. (If you have to do this, please
- './config.guess' and what the template file should be.)
+ configure again, this time giving the option to
+ make the right file be chosen.
+
+
+
Please Report Problems
+
+If your system is not automatically recognized by configure and you have to do this, please
+ send email to
+
./config.guess and also what the template file should be.)
+
+
- As an example, here is the configure script I use on a Sparc
- Solaris 2.5 system with /opt/postgres being the install base.
+ As an example, here is the configure script used on a Sparc
+ Solaris 2.5 system with /opt/postgres being the install base.
- ./configure --prefix=/opt/postgres \
- --with-template=sparc_solaris-gcc --with-pgport=5432 \
- --enable-hba --disable-locale
+$ ./configure --prefix=/opt/postgres \
+ --with-template=sparc_solaris-gcc --with-pgport=5432 \
+ --enable-hba --disable-locale
- Of course, in a real shell, you would type these three lines all
+ Of course, you may type these three lines all
on the same line.
+
+Install the
HTML documentation. Type
+
+$ cd /usr/src/pgsql/doc
+$ gmake install
+
+
+The documentation is also available in Postscript format. Look for files
+ending with .ps.gz in the same directory.
+
Compile the program. Type
+
- cd /usr/src/pgsql/src
- gmake all >& make.log &
- tail -f make.log
+$ cd /usr/src/pgsql/src
+$ gmake all >& make.log &
+$ tail -f make.log
- The last line displayed will hopefully be "All of PostgreSQL is
- successfully made. Ready to install." At this point, or earlier
+ The last line displayed will hopefully be
+All of PostgreSQL is successfully made. Ready to install.
+
+
+ At this point, or earlier
if you wish, type control-C to get out of tail. (If you have
problems later on you may wish to examine file make.log for
warning and error messages.)
-
-
- If your computer does not have gmake (GNU make) then try running
- make instead throughout the rest of these notes.
-
- Please note that you will probably find a number of warning
+
+You will probably find a number of warning
messages in make.log. Unless you have problems later on, these
messages may be safely ignored.
-Para>
+note>
- If the compiler fails with an error stating that the flex command
- cannot be found then install flex as described earlier. Next,
- change directory back to this directory, type "make clean", then
- recompile again.
+ If the compiler fails with a message stating that
+ cannot be found then install
flex as described earlier.
+ Next,
+ change directory back to this directory, type
+$ make clean
+
+then recompile again.
be specified on the command line using the COPT variable.
For example, typing
- gmake COPT="-g" all >& make.log &
+$ gmake COPT="-g" all >& make.log &
- would invoke your compiler's -g option in all steps of the
- build. See src/Makefile.global.in for further details.
+ would invoke your compiler's option in all steps of the
+ build. See src/Makefile.global.in for further details.
Install the program. Type
- cd /usr/src/pgsql/src
- gmake install >& make.install.log &
- tail -f make.install.log
+$ cd /usr/src/pgsql/src
+$ gmake install >& make.install.log &
+$ tail -f make.install.log
- The last line displayed will be "gmake[1]: Leaving directory
- `/usr/src/pgsql/src/man'". At this point, or earlier if you wish,
+ The last line displayed will be
+gmake[1]: Leaving directory `/usr/src/pgsql/src/man'
+
+At this point, or earlier if you wish,
type control-C to get out of tail.
- 14) If necessary, tell UNIX how to find your shared libraries. You can
- do ONE of the following, preferably the first:
+ 14) If necessary, tell your system how to find the new shared libraries. You can
+ do one of the following, preferably the first:
- As root, edit file /etc/ld.so.conf. Add a line
+ As root, edit file /etc/ld.so.conf. Add a line
/usr/local/pgsql/lib
to the file. Then run command /sbin/ldconfig.
+
In a bash shell, type
- If, when you create the database, you get the message "pg_id: can't
- load library 'libpq.so'" then the above step was necessary. Simply
+ If, when you create the database, you get the message
+pg_id: can't load library 'libpq.so'
+
+ then the above step was necessary. Simply
do this step, then try to create the database again.
- If it has not already been done, then prepare account postgres
+ If it has not already been done, then prepare account postgres
Any account that will use
Postgres must
be similarily prepared. (The following instructions are for a
- Add the following lines to your login shell, ~/.bash_profile:
+ Add the following lines to your login shell, ~/.bash_profile:
- PATH=$PATH:/usr/local/pgsql/bin
- MANPATH=$MANPATH:/usr/local/pgsql/man
- PGLIB=/usr/local/pgsql/lib
- PGDATA=/usr/local/pgsql/data
- export PATH MANPATH PGLIB PGDATA
+PATH=$PATH:/usr/local/pgsql/bin
+MANPATH=$MANPATH:/usr/local/pgsql/man
+PGLIB=/usr/local/pgsql/lib
+PGDATA=/usr/local/pgsql/data
+export PATH MANPATH PGLIB PGDATA
Make sure that you have defined these variables before continuing
with the remaining steps. The easiest way to do this is to type:
- source ~/.bash_profile
+$ source ~/.bash_profile
Create the database. Do not do the following as root!
This would be a major security hole. Type
- initdb
+$ initdb
Set up permissions to access the database system. Do this by editing
- file /usr/local/pgsql/data/pg_hba.conf. The instructions are
+ file /usr/local/pgsql/data/pg_hba.conf. The instructions are
included in the file. (If your database is not located in the
- default location, i.e. if PGDATA is set to point elsewhere, then the
+ default location, i.e. if PGDATA is set to point elsewhere, then the
location of this file will change accordingly.) This file should be
made read only again once you are finished.
- If you are upgrading from v6.0 or later you can copy file pg_hba.conf from
+ If you are upgrading from v6.0 or later you can copy file pg_hba.conf from
your old database on top of the one in your new database, rather than
redoing the file from scratch.
-
- The file /usr/src/pgsql/src/test/regress/README has detailed
+ Run the regression tests.
+ The file /usr/src/pgsql/src/test/regress/README has detailed
instructions for running and interpreting the regression tests.
A short version follows here:
+
+
+
+ Run postmaster from your
Postgres superuser account (typically
+ account postgres).
+
Do not run postmaster from the root account! Start the postmaster daemon running in the background by typing
$ cd
$ nohup postmaster > regress.log 2>&1 &
- Run postmaster from your
Postgres super user account (typically
- account postgres).
-
Do not run postmaster from the root account!
-
- Run the regression tests.
- (You can skip this step if you wish, but
- we think skipping the tests is a BAD idea!)
-
-
- The file /usr/src/pgsql/src/test/regress/README has detailed
- instructions for running and interpreting the regression tests.
- A short version follows here:
-
-
Type
- cd /usr/src/pgsql/src/test/regress
- gmake clean
- gmake all runtest
+$ cd /usr/src/pgsql/src/test/regress
+$ gmake clean
+$ gmake all runtest
- You do not need to type "gmake clean" if this is the first time you
+ You do not need to type gmake clean
+ if this is the first time you
are running the tests.
- You should get on the screen (and also written to file ./regress.out)
+ You should get on the screen (and also written to file ./regress.out)
a series of statements stating which tests passed and which tests
- failed. Please note that it can be normal for some of the tests to
- "fail". The script says a test has failed if there is any difference
+ failed. Please note that it can be normal for some tests to
+ "fail" on some platforms.
+The script says a test has failed if there is any difference
at all between the actual output of the test and the expected output.
Thus, tests may "fail" due to minor differences in wording of error
messages, small differences in floating-point roundoff, etc, between
your system and the regression test reference platform.
"Failures" of this type do not indicate a problem with
- The file ./regression.diffs contains the textual differences between
+ The file ./regression.diffs contains the textual differences between
the actual test output on your machine and the "expected" output
(which is simply what the reference system produced). You should
carefully examine each difference listed to see whether it appears to
be a significant issue.
+For example,
+
+
+
For a i686/Linux-ELF platform, no tests failed since this is the
v6.4 regression testing reference platform.
+
For the SPARC/Linux-ELF platform, using the 970525 beta version of
Postgres v6.2 the following tests "failed":
floating point numbers. select_views produces massively different output,
but the differences are due to minor floating point differences.
+
Even if a test result clearly indicates a real failure, it may be a
localized problem that will not affect you. An example is that the
- int8 test will fail, producing obviously incorrect output, if your
+ int8 test will fail, producing obviously incorrect output, if your
machine and C compiler do not provide a 64-bit integer data type
(or if they do but configure didn't discover it). This is not
something to worry about unless you need to store 64-bit integers.
Conclusion? If you do see failures, try to understand the nature of
the differences and then decide if those differences will affect your
intended use of
Postgres. The regression
- tests are a helpful tool, but they require some study to be useful.
+ tests are a helpful tool, but they may require some study to be useful.
After running the regression tests, type
+
- destroydb regression
- cd /usr/src/pgsql/src/test/regress
- gmake clean
+$ destroydb regression
+$ cd /usr/src/pgsql/src/test/regress
+$ gmake clean
+
to recover the disk space used for the tests. (You may want to save
- the regression.diffs file in another place before doing this.)
+ the regression.diffs file in another place before doing this.)
+
+
If you haven't already done so, this would be a good time to modify
Here are some suggestions on how to do this, contributed by various
users.
- Whatever you do, postmaster must be run by user postgres AND NOT BY
- ROOT. This is why all of the examples below start by switching user
+ Whatever you do, postmaster must be run by
+the
Postgres superuser (
postgres?)
+and not by root.
+This is why all of the examples below start by switching user
(su) to postgres. These commands also take into account the fact
that environment variables like PATH and PGDATA may not be set properly.
The examples are as follows. Use them with extreme caution.
- a) Edit file rc.local on NetBSD or file rc2.d on SPARC Solaris
+
+
+Edit file rc.local on NetBSD or file rc2.d on SPARC Solaris
2.5.1 to contain the following single line:
- su postgres -c "/usr/local/pgsql/bin/postmaster -S -D
- /usr/local/pgsql/data"
+su postgres -c "/usr/local/pgsql/bin/postmaster -S -D /usr/local/pgsql/data"
+
- b) In FreeBSD 2.2-RELEASE edit /usr/local/etc/rc.d/pgsql.sh to
+
+In FreeBSD 2.2-RELEASE edit /usr/local/etc/rc.d/pgsql.sh to
contain the following lines and make it chmod 755 and chown
root:bin.
- #!/bin/sh
- [ -x /usr/local/pgsql/bin/postmaster ] && {
- su -l pgsql -c 'exec /usr/local/pgsql/bin/postmaster
- -D/usr/local/pgsql/data
- -S -o -F > /usr/local/pgsql/errlog' &
- echo -n ' pgsql'
- }
+
+#!/bin/sh
+[ -x /usr/local/pgsql/bin/postmaster ] && {
+ su -l pgsql -c 'exec /usr/local/pgsql/bin/postmaster
+ -D/usr/local/pgsql/data
+ -S -o -F > /usr/local/pgsql/errlog' &
+ echo -n ' pgsql'
+}
+
+
You may put the line breaks as shown above. The shell is smart
enough to keep parsing beyond end-of-line if there is an
expression unfinished. The exec saves one layer of shell under
- the postmaster process so the parent is init. Note: Unlike most
- other examples, this one has been tested.
-
- c) In RedHat v4.0 Linux edit file /etc/inittab to add the
- following single line:
- pg:2345:respawn:/bin/su - postgres -c
- "/usr/local/pgsql/bin/postmaster -D/usr/local/pgsql/data
- >> /usr/local/pgsql/server.log 2>&1
+ the postmaster process so the parent is init.
+
+
+In RedHat Linux add a file /etc/rc.d/init.d/postgres.init
+which is based on the example in contrib/linux/.
+Then make a softlink to this file from
+ /etc/rc.d/rc5.d/S98postgres.init.
+
+
+In RedHat Linux edit file /etc/inittab to add the
+ following as a single line:
+
+pg:2345:respawn:/bin/su - postgres -c
+ "/usr/local/pgsql/bin/postmaster -D/usr/local/pgsql/data
+ >> /usr/local/pgsql/server.log 2>&1 </dev/null"
+
+
(The author of this example says this example will revive the
postmaster if it dies, but he doesn't know if there are other side
effects.)
- d) The contrib/linux area of the
Postgres distribution has an example
- init.d script compatible with and tested using recent RedHat packages.
+
+
-Run the SQL command vacuum. This will clean up your database.
+Run the
SQL command
VACUUM.
+This will clean up your database.
Ideally, the above tasks should be done by a shell script that is
- run nightly or weekly by cron. Look at the man page for crontab
+ run nightly or weekly by cron.
+Look at the man page for
crontab for a starting point on how to do this. (If you do it, please
e-mail us a copy of your shell script. We would like to set up
our own systems to do this too.)
If you are upgrading an existing system then reinstall your old database.
Type
- cd
- psql -e template1 < db.out
+$ cd
+$ psql -e template1 < db.out
If your pre-v6.2 database uses either path or polygon geometric data types,
then you will need to upgrade any columns containing those types. To
do so, type (from within psql)
- update YourTable set PathCol = UpgradePath(PathCol);
- update YourTable set PolyCol = UpgradePoly(PolyCol);
- ...
- vacuum;
+UPDATE FirstTable SET PathCol = UpgradePath(PathCol);
+UPDATE SecondTable SET PathCol = UpgradePath(PathCol);
+...
+VACUUM;
UpgradePath() checks to see that a path value is consistant with the
Clean up after yourself. Type
- rm -rf /usr/src/pgsql_6_0
- rm -rf /usr/local/pgsql_6_0
- # Also delete old database directory tree if it is not in
- # /usr/local/pgsql_6_0/data
- rm ~/postgresql-v6.2.1.tar.gz
+$ rm -rf /usr/src/pgsql_6_0
+$ rm -rf /usr/local/pgsql_6_0
+# Also delete old database directory tree if it is not in
+# /usr/local/pgsql_6_0/data
+$ rm ~/postgresql-v6.2.1.tar.gz
- You will probably want to print out the documentation. Here is how
+ You will probably want to print out the documentation. If you have
+a Postscript printer, or have your machine already set up to accept
+Postscript files using a print filter, then to print the User's Guide
+simply type
+
+$ cd /usr/local/pgsql/doc
+$ gunzip user.ps.tz | lpr
+
+
+ Here is how
you might do it if you have Ghostscript on your system and are
writing to a laserjet printer.
- alias gshp='gs -sDEVICE=laserjet -r300 -dNOPAUSE'
- export GS_LIB=/usr/share/ghostscript:/usr/share/ghostscript/fonts
- # Print out the man pages.
- man -a -t /usr/local/pgsql/man/*/* > manpage.ps
- gshp -sOUTPUTFILE=manpage.hp manpage.ps
- rm manpage.ps
- lpr -l -s -r manpage.hp
- # Print out the Postgres95 User Manual, version 1.0,
- # Sept. 5, 1996.
- cd /usr/src/pgsql/doc
- gshp -sOUTPUTFILE=userguide.hp userguide.ps
- lpr -l -s -r userguide.hp
+$ alias gshp='gs -sDEVICE=laserjet -r300 -dNOPAUSE'
+$ export GS_LIB=/usr/share/ghostscript:/usr/share/ghostscript/fonts
+$ gunzip user.ps.gz
+$ gshp -sOUTPUTFILE=user.hp user.ps
+$ gzip user.ps
+$ lpr -l -s -r manpage.hp
supported platforms. We therefore ask you to let us know if you did
or did not get
Postgres to work on you system.
Please send a
+ mail message to
+ telling us the following:
- % psql template1
+% psql template1
(psql has to open a particular database, but at this point the only one
-For some ports, these notes may be out of date.
+Check for any platform-specific FAQs in the doc/ directory of
+the source distribution. For some ports, the notes below may be out of date.
Ultrix4.x
+
+There have been no recent reports of Ultrix usage with
Postgres.
+
+
You need to install the libdl-1.1 package since Ultrix 4.x doesn't
have a dynamic loader. It's available in
s2k-ftp.CS.Berkeley.EDU:pub/personal/andrew/libdl-1.1.tar.Z
-We have no recent reports of successful NeXT installations (for v6.2.1).
+We have no recent reports of successful NeXT installations (as of v6.2.1).
However, the client-side libraries should work even
if the backend is not supported.
projects / postgresql.git / commitdiff