Doc: remove obsolete advice about manually inserting snprintf into build.

This para is obsolete, first because nobody is using Solaris 7 anymore,
and second because if someone was, configure should catch the snprintf
buffer overrun problem automatically (since commit 9bed827b), and third
because this is incorrect advice about how to manually force use of
snprintf.c anyway, and has been so at least since commit 3bc6bdf3.
The lack of complaints about it reinforces the conclusion that Solaris 7
no longer exists in the wild; so I don't feel a need to insert correct
advice instead.

doc/src/sgml/installation.sgml

@@ -2636,30 +2636,6 @@ configure ... LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
     </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 <function>vsnprintf</function> 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>