14) If necessary, tell UNIX how to find your shared libraries. You can
do ONE of the following, preferably the first:
+
- As root, edit file /etc/ld.so.conf. Add line
- /usr/local/pgsql/lib
- to the file. Then run command /sbin/ldconfig.
+ As root, edit file /etc/ld.so.conf. Add a line
+/usr/local/pgsql/lib
+
+to the file. Then run command /sbin/ldconfig.
If it has not already been done, then prepare account postgres
- for using
Postgres. Any account that will use
Postgres must
+Any account that will use
Postgres must
be similarily prepared. (The following instructions are for a
bash shell. Adapt accordingly for other shells.)
- Start the postmaster daemon running. Type
+ The file /usr/src/pgsql/src/test/regress/README has detailed
+ instructions for running and interpreting the regression tests.
+ A short version follows here:
+
+
+ Start the postmaster daemon running in the background by typing
- cd
- nohup postmaster > server.log 2>&1 &
+$ 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.
+ account postgres).
+
Do not run postmaster from the root account!
your computer to do regular maintainence. The following should be
done at regular intervals:
- a) Run the SQL command vacuum. This will clean up your database.
- b) Back up your system. (You should probably keep the last few
- backups on hand.) Ideally, no one else should be using the
+
Minimal Backup Procedure
+
+
+Run the SQL command vacuum. This will clean up your database.
+
+
+Back up your system. (You should probably keep the last few
+ backups on hand.) Preferably, no one else should be using the
system at the time.
+
+
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
for a starting point on how to do this. (If you do it, please
You will probably want to print out the documentation. 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.
cd /usr/src/pgsql/doc
gshp -sOUTPUTFILE=userguide.hp userguide.ps
lpr -l -s -r userguide.hp
+
- If you are a developer, you will probably want to also print out
- the Postgres Implemention Guide, version 1.0, October 1, 1995.
- This is a WWW document located at
- http://www.postgresql.org/docs/impguide.
-
- The
Postgres team wants to keep
Postgres working on all of the
+ The
Postgres team wants
+ to keep
Postgres working on all of the
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
+ or did not get
Postgres to work on you system.
+ Please send a
- - The version of
Postgres (v6.2.1, 6.1.1, beta 970703, etc.).
- - Your operating system (i.e. RedHat v4.0 Linux v2.0.26).
- - Your hardware (SPARC, i486, etc.).
- - Did you compile, install and run the regression tests cleanly?
+
+
+
+The version of
Postgres (v6.4, 6.3.2, beta 981014, etc.).
+
+
+Your operating system (i.e. RedHat v5.1 Linux v2.0.34).
+
+
+Your hardware (SPARC, i486, etc.).
+
+
+Did you compile, install and run the regression tests cleanly?
If not, what source code did you change (i.e. patches you
applied, changes you made, etc.), what tests failed, etc.
It is normal to get many warning when you compile. You do
not need to report these.
+
+
+
Now create, access and manipulate databases as desired. Write client
- programs to access the database server. In other words, ENJOY!
+ programs to access the database server. In other words, enjoy!