Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 840B664FCE6
	for <pgsql-es-ayuda-postgresql.org@mail.postgresql.org>;
	Tue, 18 Nov 2008 08:02:23 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 52019-05
	for <pgsql-es-ayuda-postgresql.org@mail.postgresql.org>;
	Tue, 18 Nov 2008 08:02:20 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from wf-out-1314.google.com (wf-out-1314.google.com
 [209.85.200.169])
	by mail.postgresql.org (Postfix) with ESMTP id CE06A64FC8B
	for <pgsql-es-ayuda@postgresql.org>;
	Tue, 18 Nov 2008 08:02:19 -0400 (AST)
Received: by wf-out-1314.google.com with SMTP id 25so3007062wfc.28
	for <pgsql-es-ayuda@postgresql.org>;
	Tue, 18 Nov 2008 04:02:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=1HXrJIS8wvA2AvnI82qaAerc1cgx5qAEx36fX9NAlnk=;
	b=HwYB0IG1ZoJ3tOcb3eSLZYon9IIg3LwWq3jB5745CkgQvq95qf+PpHoADo+lSnsBdH
	quVFu8dM8VjXguFGAAQTlDHVIbAvt/pQ6hsFHzVc1TJz3Zx/3bU09V+KzC5+Zx5jaN0X
	3ynMihTxh95bEMNyHgHd4kYkaSTdEWusbF01w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=IEnyo47peQY8hkD5q/ymD6oCw0bXm+p3Hh8Q1iDVW75lxpq0QWMYu+j+HqLvwZnAls
	KH7ibIYjCw0UFGfIWrDMh90FQu2aso196Y/bHa++zJI6sGQLZi+p+tvCTR38XKg0mL9z
	Yl0AKUjQ1u/Jd/eV1go1In0u4lzODCGfwzlIs=
Received: by 10.142.174.8 with SMTP id w8mr2560936wfe.76.1227009737974;
	Tue, 18 Nov 2008 04:02:17 -0800 (PST)
Received: by 10.142.237.5 with HTTP; Tue, 18 Nov 2008 04:02:17 -0800 (PST)
Message-ID: <f205bb120811180402u4471131xef761a3b9ca7dcd6@mail.gmail.com>
Date: Tue, 18 Nov 2008 10:02:17 -0200
From: "Emanuel CALVO FRANCO" <postgres.arg@gmail.com>
To: pgsql-es-ayuda <pgsql-es-ayuda@postgresql.org>
Subject: Re: [DOCS] FAQ_Solaris 1.28 to spanish
In-Reply-To: <49229772.5090706@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com>
	<200811012216.51622.peter_e@gmx.net> <49229772.5090706@gmx.net>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=WHOIS_NETSOLPR=0.001
X-Spam-Level: 
X-Archive-Number: 200811/489
X-Sequence-Number: 39003

i will be working on that next week.

2008/11/18 Peter Eisentraut <peter_e@gmx.net>:
> Peter Eisentraut wrote:
>>>
>>> I have new things to add, specially for Open Solaris plattaform
>>> specifications. I can write a new FAQ or just concatenate to this the
>>> other
>>> features of OSolaris?
>>
>> In my opinion, the platform FAQs should be scrapped and the information
>> should be placed into the real documentation at the appropriate places.
>
> Here is a beginning patch of what I am planning to do with the platform FAQs
> in terms of getting it integrated into the main documentation.  If you don't
> like where this is going, please speak up.
>
> Index: doc/src/sgml/installation.sgml
> ===================================================================
> RCS file: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v
> retrieving revision 1.313
> diff -u -3 -p -r1.313 installation.sgml
> --- doc/src/sgml/installation.sgml      5 Sep 2008 12:11:18 -0000
> 1.313
> +++ doc/src/sgml/installation.sgml      18 Nov 2008 10:18:03 -0000
> @@ -2001,8 +2001,9 @@ kill `cat /usr/local/pgsql/data/postmast
>    FreeBSD, OpenBSD, NetBSD, Mac OS X, AIX, HP/UX, IRIX, Solaris, Tru64
> Unix,
>    and UnixWare.  Other Unix-like systems may also work but are not
> currently
>    being tested.  In most cases, all CPU architectures supported by
> -   a given operating system will work.  Look in the <filename>doc/</>
> -   directory of the source distribution to see if there is a FAQ document
> +   a given operating system will work.  Look in
> +   the <xref linkend="installation-platform-notes"> below to see if
> +   there is information
>    specific to your operating system, particularly if using an older system.
>   </para>
>
> @@ -2011,9 +2012,202 @@ kill `cat /usr/local/pgsql/data/postmast
>    to be supported according to recent build farm results, please report
>    it to <email>pgsql-bugs@postgresql.org</email>.  If you are interested
>    in porting <productname>PostgreSQL</> to a new platform,
> -   <email>pgsql-ports@postgresql.org</email> is the appropriate place
> +   <email>pgsql-hackers@postgresql.org</email> is the appropriate place
>    to discuss that.
>   </para>
>  </sect1>
>
> + <sect1 id="installation-platform-notes">
> +  <title>Platform-Specific Notes</title>
> +
> +  <sect2 id="installation-notes-solaris">
> +   <title>Solaris</title>
> +
> +   <sect3>
> +    <title>Required tools</title>
> +
> +    <para>
> +     To build and install PostgreSQL on Solaris, you will need
> +     <itemizedlist>
> +      <listitem><para>gzip (for installing the
> documentation)</para></listitem>
> +      <listitem><para>GNU Make</para></listitem>
> +      <listitem><para>GNU Readline library (optional)</para></listitem>
> +      <listitem><para>Sun Studio CC or GCC</para></listitem>
> +     </itemizedlist>
> +
> +     You can download Sun Studio
> +     from <ulink
> url="http://developers.sun.com/sunstudio/downloads/"></ulink>.
> +     Many of GNU tools are integrated into Solaris 10, or they are
> +     present on the Solaris companion CD.  If you like packages for
> +     older version of Solaris, you can find these tools
> +     at <ulink url="http://www.sunfreeware.com"></ulink>
> +     or <ulink url="http://www.blastwave.org"></ulink>.  If you prefer
> +     sources, look
> +     at <ulink url="http://www.gnu.org/order/ftp.html"></ulink>.
> +    </para>
> +
> +    <para>
> +     You can build with either GCC or Sun's compiler suite.  For
> +     better code optimization, Sun's compiler is strongly recommended
> +     on the SPARC architecture.  We have heard reports of problems
> +     when using GCC 2.95.1; gcc 2.95.3 or later is recommended.  If
> +     you are using Sun's compiler, be careful not to select
> +     <filename>/usr/ucb/cc</filename>;
> +     use <filename>/opt/SUNWspro/bin/cc</filename>.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>Problems with OpenSSL</title>
> +
> +    <para>
> +     When you build PostgreSQL with OpenSSL support you might get
> +     compilation errors in the following files:
> +     <itemizedlist>
> +
>  <listitem><para><filename>src/backend/libpq/crypt.c</filename></para></listitem>
> +
>  <listitem><para><filename>src/backend/libpq/password.c</filename></para></listitem>
> +
>  <listitem><para><filename>src/interfaces/libpq/fe-auth.c</filename></para></listitem>
> +
>  <listitem><para><filename>src/interfaces/libpq/fe-connect.c</filename></para></listitem>
> +     </itemizedlist>
> +
> +     This is because of a namespace conflict between the standard
> +     <filename>/usr/include/crypt.h</filename> header and the header
> +     files provided by OpenSSL.
> +    </para>
> +
> +    <para>
> +     Upgrading your OpenSSL installation to version 0.9.6a fixes this
> +     problem.  Solaris 9 and above has a newer version of OpenSSL.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>configure complains about a failed test program</title>
> +
> +    <para>
> +     If configure complains about a failed test program, 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 <envar>LDFLAGS</envar> environment variable, e.g.,
> +<programlisting>
> +LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
> +export LDFLAGS
> +</programlisting>
> +     and restart configure.  See
> +     the <citerefentry><refentrytitle>ld</><manvolnum>1</></citerefentry>
> +     man page for more information.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>64-bit build sometimes crashes</title>
> +
> +    <para>
> +     On Solaris 7 and older, the 64-bit version of libc has a buggy
> +     <function>vsnprintf</function> routine, which leads to erratic
> +     core dumps in PostgreSQL.  The simplest known workaround is to
> +     force PostgreSQL to use its own version of vsnprintf rather than
> +     the library copy.  To do this, after you
> +     run <command>configure</command> edit a file produced by
> +     <command>configure</command>:
> +     In <filename>src/Makefile.global</filename>, change the line
> +<programlisting>
> +LIBOBJS =
> +</programlisting>
> +     to read
> +<programlisting>
> +LIBOBJS = snprintf.o
> +</programlisting>
> +     (There might be other files already listed in this variable.
> +     Order does not matter.)  Then build as usual.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>Compiling for optimal performance</title>
> +
> +    <para>
> +     On the SPARC architecture, Sun Studio is strongly recommended for
> +     compilation.  Try using the <option>-xO5</option> optimization
> +     flag to generate significantly faster binaries.  Do not use any
> +     flags that modify behavior of floating-point operations
> +     and <varname>errno</varname> processing (e.g.,
> +     <option>-fast</option>).  These flags could raise some
> +     nonstandard PostgreSQL behavior for example in the date/time
> +     computing.
> +    </para>
> +
> +    <para>
> +     If you do not have a reason to use 64-bit binaries on SPARC,
> +     prefer the 32-bit version.  The 64-bit operations are slower and
> +     64-bit binaries are slower than the 32-bit variants.  And on
> +     other hand, 32-bit code on the AMD64 CPU family is not native,
> +     and that is why 32-bit code is significant slower on this CPU
> +     family.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>Solaris packages</title>
> +
> +    <para>
> +     PostgreSQL is bundled with Solaris 10 (from update 2).  Official
> +     packages are also available on
> +     <ulink url="http://pgfoundry.org/projects/solarispackages/"></ulink>.
> +     Packages for older Solaris versions (8, 9) you can be obtained
> +     from <ulink url="http://www.sunfreeware.com/"></ulink> or
> +     <ulink url="http://www.blastwave.org/"></ulink>.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>Performance tuning</title>
> +
> +    <para>
> +     Some tricks for tuning PostgreSQL and Solaris for performance can
> +     be found
> +     at <ulink
> url="http://www.sun.com/servers/coolthreads/tnb/applications_postgresql.jsp"></ulink>.
> +     This article is primary focused on T2000 platform, but many of
> +     the recommendations are also useful on other hardware with
> +     Solaris.
> +    </para>
> +   </sect3>
> +
> +   <sect3>
> +    <title>Using DTrace for tracing PostgreSQL</title>
> +
> +    <para>
> +     Yes, using DTrace is possible.  See <xref linkend="monitoring">
> +     for further information.  You can also find more information in
> +     this
> +     article: <ulink
> url="http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in"></ulink>.
> +    </para>
> +
> +    <para>
> +     If you see the linking of the postgres executable abort with an
> +     error message like
> +<screen>
> +Undefined                       first referenced
> + symbol                             in file
> +AbortTransaction                    utils/probes.o
> +CommitTransaction                   utils/probes.o
> +ld: fatal: Symbol referencing errors. No output written to postgres
> +collect2: ld returned 1 exit status
> +gmake: *** [postgres] Error 1
> +</screen>
> +     your DTrace installation is too old to handle probes in static
> +     functions.  You need Solaris 10u4 or newer.  A workaround is to
> +     remove the
> +     <literal>static</literal> key word from the function declarations
> +     of <function>AbortTransaction</function>
> +     and <function>CommitTransaction</function>
> +     in <filename>src/backend/access/transam/xact.c</filename>.  See
> +     also <ulink
> url="http://sunsolve.sun.com/search/document.do?assetkey=1-1-2139224-1"></ulink>
> +     (registration required).
> +    </para>
> +   </sect3>
> +  </sect2>
> + </sect1>
> +
>  </chapter>
>
>



-- 
    Emanuel Calvo Franco
   Syscope Postgresql DBA
     BaPUG / AOSUG Member