Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ - Mailing list pgsql-patches
From | Zdenek Kotala |
---|---|
Subject | Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ |
Date | |
Msg-id | 45DF133D.2010606@sun.com Whole thread Raw |
Responses |
Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ
(Bruce Momjian <bruce@momjian.us>)
Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ (Peter Eisentraut <peter_e@gmx.net>) Re: [BUGS] BUG #2969: Inaccuracies in Solaris FAQ (Rich Teer <rich.teer@rite-group.com>) |
List | pgsql-patches |
There is Solaris FAQ update. Please, look on it and let me know any comments. Thanks Zdenek Rich Teer wrote: > The following bug has been logged online: > > Bug reference: 2969 > Logged by: Rich Teer > Email address: rich.teer@rite-group.com > PostgreSQL version: 8.2.2 > Operating system: Solaris 10 > Description: Inaccuracies in Solaris FAQ > Details: > > Hi there, > > First, many thanks for providing the best open source database! I've > spotted a couple of errors/bits of bad advice in doc/FAQ_Solaris, which I > think should be updated. > > 1. The answer to question 3 (Why does configure complain about a failed test > program?) says to set LD_LIBRARY_PATH to point to the directory containing > the missing libs. While this does work (as does the other suggestion of > using LD_RUN_PATH), the correct answer to this question is to include the > library's path in the executable by using the -R flag, thus avoiding the > need for the end user to mess about with environment variables. For > example, I use "LDFLAGS=-R/usr/sfw/lib ./configure ..." to build Postgres > which uses Sun's OpenSSL. > > 2. The answer to question 8 (Can I use DTrace for tracing PostgreSQL?) says > that Solaris 10u3 or newer is required to handle probes in static functions. > Unfortunately, this is not the case. DTrace can't be enabled when using > update 3 (aka 11/06); the (as yet unreleased) update 4 or newer is > required. > > Thanks for reading! > > Rich Teer, > Author of Solaris Systems Programming > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster Index: doc/FAQ_Solaris =================================================================== RCS file: /projects/cvsroot/pgsql/doc/FAQ_Solaris,v retrieving revision 1.23 diff -c -r1.23 FAQ_Solaris *** doc/FAQ_Solaris 2 Dec 2006 09:29:51 -0000 1.23 --- doc/FAQ_Solaris 23 Feb 2007 16:12:19 -0000 *************** *** 16,21 **** --- 16,22 ---- 6) Where I can download prepared Solaris packages? 7) How can I tune PostgreSQL and Solaris for performance? 8) Can I use DTrace for tracing PostgreSQL? + 9) Can I compile PostgreSQL with Kerberos v5 support? 1) What tools do I need to build and install PostgreSQL on Solaris? *************** *** 72,85 **** This is probably a case of the run-time linker being unable to find some library, probably libz, libreadline or some other non-standard library such as libssl. To point it to the right location, set the ! LD_LIBRARY_PATH environment variable, e.g., ! LD_LIBRARY_PATH=/usr/sfw/lib:/opt/sfw/lib:/usr/local/lib ! export LD_LIBRARY_PATH ! and restart configure. You will also have to keep this setting whenever ! you run any of the installed PostgreSQL programs. Alternatively, set ! the environment variable LD_RUN_PATH. See the ld(1) man page for more information. --- 73,84 ---- This is probably a case of the run-time linker being unable to find some library, probably libz, libreadline or some other non-standard library such as libssl. To point it to the right location, set the ! LDFLAGS environment variable, e.g., ! LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib" ! export LDFLAGS ! and restart configure. See the ld(1) man page for more information. *************** *** 145,150 **** --- 144,153 ---- Yes, see the chapter "Monitoring Database Activity" in the documentation for further information. + You can also find more information here: + + http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in + If you see the linking of the postgres executable abort with an error message like *************** *** 157,164 **** gmake: *** [postgres] Error 1 your DTrace installation is too old to handle probes in static ! functions. You need Solaris 10u3 or newer. - You can also find more information here: - - http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in --- 160,176 ---- gmake: *** [postgres] Error 1 your DTrace installation is too old to handle probes in static ! functions. You need Solaris 10u4 or newer. Workaround is remove static ! keyword from AbortTransaction and CommitTransaction functions declaration in ! src/backend/access/transam/xact.c. ! ! See http://sunsolve.sun.com/search/document.do?assetkey=1-1-2139224-1 ! (registration required). ! ! 9) Can I compile PostgreSQL with Kerberos v5 support? ! ! Kerberos is integrated in OpenSolaris and will be integrated in Solaris 10u4. GSS security ! mechanism contains internal Kerberos v5 library implementation which provide all necessary ! krb5 function. However, usage this library is only on own risk. It is private library ! and interface may change without notice.
pgsql-patches by date: