Re: BUG #2969: Inaccuracies in Solaris FAQ

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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-21 14:28:06
Message-ID: 45DC56F6.6040507@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

I work on it. It will be ready until Friday.

Zdenek

Bruce Momjian wrote:
> 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
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Koterov 2007-02-21 16:20:42 BUG #3048: pg_dump dumps intarray metadata incorrectly
Previous Message Cedric Scott 2007-02-21 13:18:36 BUG #3046: odbc zip file corrupt

Browse pgsql-patches by date

  From Date Subject
Next Message Markus Schiltknecht 2007-02-21 14:32:12 Re: tsearch in core patch, for inclusion
Previous Message Bruce Momjian 2007-02-21 14:01:51 Re: tsearch in core patch, for inclusion