Skip site navigation (1) Skip section navigation (2)

Re: BUG #2969: Inaccuracies in Solaris FAQ

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Rich Teer <rich(dot)teer(at)rite-group(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2969: Inaccuracies in Solaris FAQ
Date: 2007-02-19 21:25:36
Message-ID: 200702192125.l1JLPad18216@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
I have not seen an updated patch for FAQ_Solaris yet.

---------------------------------------------------------------------------

Zdenek Kotala wrote:
> Rich Teer wrote:
> > The following bug has been logged online:
> > 
> > Bug reference:      2969
> > Logged by:          Rich Teer
> > Email address:      rich(dot)teer(at)rite-group(dot)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.
> 
> Yes you have right we use -R for official Solaris package as well.  Good 
> comment.
> 
> > 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.
> 
> Original plan was release new version of DTrace in the update 3. Thanks 
> for comment. But if you want to use Dtrace on Solaris 10u3 or older you 
> can remove static from affected function in the transaction manager. It 
> is not much clean but it works.
> 
> 	
> Thanks for the comments and I will prepare a patch asap together with 
> another improvements.
> 
> 
> 	Thanks Zdenek
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
> 
>                 http://www.postgresql.org/about/donate

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-bugs by date

Next:From: JessicaDate: 2007-02-19 21:53:26
Subject: BUG #3034: FATAL: could not open lock file "/tmp/.s.PGSQL.5432.lock": Permission denied
Previous:From: Bruce MomjianDate: 2007-02-19 20:46:38
Subject: Re: BUG #2973: Compile Error with MIPSpro compiler

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-02-19 21:36:51
Subject: Re: [previously on HACKERS] "Compacting" a relation
Previous:From: Greg SmithDate: 2007-02-19 20:23:27
Subject: Re: [PATCHES] WIP patch - INSERT-able log statements

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group