Skip to content
Snippets Groups Projects
  1. Oct 05, 2006
    • Tom Lane's avatar
      Second try at fixing libedit configuration for Bob Friesenhahn. · 9e6c3582
      Tom Lane authored
      Buildfarm results from 'gazelle' show that there are indeed libedit
      versions for which history.h is a needed header, even though it's
      apparently been dropped entirely in other versions.  Grumble.
      9e6c3582
    • Tom Lane's avatar
      Adjust configure's handling of libedit to not look for a history.h file. · bdef2bf2
      Tom Lane authored
      Per Bob Friesenhahn's report, this file is not supplied by some versions
      of libedit, and even when it is supplied it seems to be just a link to
      readline.h, so we don't need to include it anyway.
      Also, ensure that we won't try to use a too-old version of Bison.
      The previous coding would bleat but then use it anyway; better to invoke
      the 'missing' script if any grammar files need to be rebuilt.
      bdef2bf2
  2. Oct 04, 2006
    • Tom Lane's avatar
      Switch over to using our own qsort() all the time, as has been proposed · 6edd2b4a
      Tom Lane authored
      repeatedly.  Now that we don't have to worry about memory leaks from
      glibc's qsort, we can safely put CHECK_FOR_INTERRUPTS into the tuplesort
      comparators, as was requested a couple months ago.  Also, get rid of
      non-reentrancy and an extra level of function call in tuplesort.c by
      providing a variant qsort_arg() API that passes an extra void * argument
      through to the comparison routine.  (We might want to use that in other
      places too, I didn't look yet.)
      6edd2b4a
  3. Oct 02, 2006
  4. Sep 27, 2006
  5. Sep 23, 2006
  6. Sep 09, 2006
  7. Aug 23, 2006
  8. Aug 17, 2006
  9. Aug 04, 2006
  10. Jul 27, 2006
  11. Jul 24, 2006
  12. Jul 11, 2006
  13. Jun 18, 2006
    • Tom Lane's avatar
      Don't try to call posix_fadvise() unless <fcntl.h> supplies a declaration · 1e8ae136
      Tom Lane authored
      for it.  Hopefully will fix core dump evidenced by some buildfarm members
      since fadvise patch went in.  The actual definition of the function is not
      ABI-compatible with compiler's default assumption in the absence of any
      declaration, so it's clearly unsafe to try to call it without seeing a
      declaration.
      1e8ae136
  14. Jun 08, 2006
    • Bruce Momjian's avatar
      Prepare code to be built by MSVC: · 399a36a7
      Bruce Momjian authored
      	o  remove many WIN32_CLIENT_ONLY defines
      	o  add WIN32_ONLY_COMPILER define
      	o  add 3rd argument to open() for portability
      	o  add include/port/win32_msvc directory for
      	   system includes
      
      Magnus Hagander
      399a36a7
  15. May 30, 2006
  16. May 23, 2006
  17. Apr 29, 2006
  18. Apr 27, 2006
  19. Apr 22, 2006
  20. Apr 19, 2006
    • Tom Lane's avatar
      Remove use of lorder and tsort while building static libraries. There's · 04ca4caa
      Tom Lane authored
      no evidence that any currently-supported platform needs this, and good
      reason to think that any platform that did need it couldn't use the static
      libraries anyway --- libpq, at least, has circular references.  Removing
      the code shuts up tsort warnings about the circular references on some
      platforms.
      04ca4caa
  21. Apr 07, 2006
    • Andrew Dunstan's avatar
      · 39ec43a2
      Andrew Dunstan authored
      Revert getaddrinfo configure changes until we get a solution that is
      properly tested on Tru64 - pre recent discussion (or lack thereof) on -hackers.
      39ec43a2
  22. Mar 06, 2006
  23. Mar 05, 2006
  24. Feb 28, 2006
  25. Feb 21, 2006
  26. Feb 15, 2006
  27. Feb 10, 2006
  28. Feb 07, 2006
  29. Feb 04, 2006
  30. Feb 03, 2006
  31. Jan 18, 2006
  32. Jan 12, 2006
    • Tom Lane's avatar
      Use a more bulletproof test for whether finite() and isinf() are present. · db0558c1
      Tom Lane authored
      It seems that recent gcc versions can optimize away calls to these functions
      even when the functions do not exist on the platform, resulting in a bogus
      positive result.  Avoid this by using a non-constant argument and ensuring
      that the function result is not simply discarded.  Per report from
      François Laupretre.
      db0558c1
Loading