11============================================================
2- Frequently Asked Questions (FAQ) for PostgreSQL V7 .1
2+ Frequently Asked Questions (FAQ) for PostgreSQL7 .1
33Sun Solaris specific
44to be read in conjunction with the installation instructions
55============================================================
6- last updated: $Date: 2001/03/13 20:42:11 $
6+ last updated: $Date: 2001/04/04 20:02:31 $
77
88current maintainer: Marc Liyanage (liyanage@access.ch)
99original author: Marc Liyanage (liyanage@access.ch)
@@ -13,6 +13,9 @@ Contents:
1313
14141) What tools do I need to build and install PostgreSQL on Solaris?
15152) Why do I get problems when building with OpenSSL support?
16+ 3) Why does configure complain about a failed test program?
17+ 4) A bunch of regression tests fail in random, non-reproduceable
18+ patterns. What's wrong?
1619
1720
18211) What tools do I need to build and install PostgreSQL on Solaris?
@@ -48,3 +51,36 @@ We believe that this should be fixed by OpenSSL.
4851
4952The problem can be worked around by removing the inclusion of
5053<crypt.h> in these four files.
54+
55+
56+ 3) Why does configure complain about a failed test program?
57+
58+ This is probably a case of the run-time linker being unable to find
59+ libz or some other non-standard library, such as libssl. To point it
60+ to the right location, set the LD_LIBRARY_PATH environment variable,
61+ e.g.,
62+
63+ LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib
64+ export LD_LIBRARY_PATH
65+
66+ and restart configure. You will also have to keep this setting
67+ whenever you run any of the installed PostgreSQL programs.
68+
69+ In the future, consider installing the offending libraries so they
70+ provide their own "rpath".
71+
72+
73+ 4) A bunch of regression tests fail in random, non-reproduceable
74+ patterns. What's wrong?
75+
76+ A lot of users have reported that the parallel regression test suite
77+ causes a varying, unpredictable set of tests to fail, usually tests in
78+ the second half of the run. The failure is usually a failure to
79+ connect to the server at all, or an abrupt loss of the connection.
80+ Invariably, these problems go away when the regression test suite is
81+ changed to use TCP/IP sockets instead of Unix domain sockets. (Change
82+ line 163 of src/test/regress/pg_regress to match *solaris*; yes, there
83+ should be an easier way to do this.) Since a number of users do not
84+ seem to have any problems with this at all, we do not claim that "Unix
85+ domain sockets are broken on Solaris", but feel free to draw your own
86+ conclusions, or better yet, share your insights with the rest of us.