From 47183265ed745d9ee7e0ac0798a5c88660436d4e Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 18 Aug 2018 14:02:35 -0400 Subject: [PATCH] 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 9bed827b1), 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 3bc6bdf32. 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 | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index a88cd21f45..10c925d290 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -2636,30 +2636,6 @@ configure ... LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib" - - 64-bit Build Sometimes Crashes - - - On Solaris 7 and older, the 64-bit version of libc has a buggy - vsnprintf 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 configure edit a file produced by - configure: - In src/Makefile.global, change the line - -LIBOBJS = - - to read - -LIBOBJS = snprintf.o - - (There might be other files already listed in this variable. - Order does not matter.) Then build as usual. - - - Compiling for Optimal Performance