1. 19 Feb, 2002 1 commit
  2. 25 Oct, 2001 1 commit
  3. 22 Mar, 2001 1 commit
  4. 03 Dec, 2000 1 commit
  5. 25 Nov, 2000 2 commits
    • Tom Lane's avatar
      Make PGLC_setlocale() static, and document that it can't be used safely · e3269cab
      Tom Lane authored
      for any other purpose than PGLC_localeconv()'s internal save/restore of
      locale settings.  Fix cash.c to call PGLC_localeconv() rather than
      making a direct call to localeconv() --- the old way, if PGLC_localeconv()
      had already cached a locale result, it would be overwritten by the first
      cash_in or cash_out operation, leading to wrong-locale results later.
      Probably no demonstrable bug today, since we only appear to be looking
      at the LC_MONETARY results which should be the same anyway, but definitely
      a gotcha waiting to strike.
      e3269cab
    • Tom Lane's avatar
      Store current LC_COLLATE and LC_CTYPE settings in pg_control during initdb; · bbea3643
      Tom Lane authored
      re-adopt these settings at every postmaster or standalone-backend startup.
      This should fix problems with indexes becoming corrupt due to failure to
      provide consistent locale environment for postmaster at all times.  Also,
      refuse to start up a non-locale-enabled compilation in a database originally
      initdb'd with a non-C locale.  Suppress LIKE index optimization if locale
      is not "C" or "POSIX" (are there any other locales where it's safe?).
      Issue NOTICE during initdb if selected locale disables LIKE optimization.
      bbea3643
  6. 18 Nov, 2000 1 commit
    • Tom Lane's avatar
      Modify locale code to defend against possibility that it was compiled · 75c147e7
      Tom Lane authored
      with an -fsigned-char/-funsigned-char setting opposite to that of libc,
      thus breaking the convention that 'undefined' values returned by
      localeconv() are represented by CHAR_MAX.  It is sheer stupidity that
      gcc even has such a switch --- it's just as bad as the structure-packing
      control switches offered by the more brain-dead PC compilers --- and
      as for the behavior of Linux distribution vendors who set RPM_OPT_FLAGS
      differently from the way they built libc, well, words fail me...
      75c147e7
  7. 03 Aug, 2000 1 commit
  8. 01 Aug, 2000 1 commit
  9. 07 Jul, 2000 1 commit
  10. 06 Jul, 2000 1 commit
  11. 03 Jul, 2000 1 commit
    • Jan Wieck's avatar
      TOAST · 57d8080a
      Jan Wieck authored
          WARNING: This is actually broken - we have self-deadlocks
      	         due to concurrent changes in buffer management.
      			 Vadim and me are working on it.
      
      Jan
      57d8080a
  12. 15 Jun, 2000 1 commit
  13. 14 Jun, 2000 1 commit
    • Peter Eisentraut's avatar
      Big warnings cleanup for Solaris/GCC. Down to about 40 now, but · 44d1abeb
      Peter Eisentraut authored
      we'll get there one day.
      
      Use `cat' to create aclocal.m4, not `aclocal'. Some people don't
      have automake installed.
      
      Only run the autoconf rule in the top-level GNUmakefile if the
      invoker specified `make configure', don't run it automatically
      because of CVS timestamp skew.
      44d1abeb
  14. 13 Jun, 2000 1 commit
  15. 05 Jun, 2000 1 commit
  16. 16 May, 2000 1 commit
    • Bruce Momjian's avatar
      Several compilation and run-time problems occur when building on SGI · a47e20b0
      Bruce Momjian authored
      IRIX systems using the native compilers.  A summary is:
      - Various files use "//" as a comment delimiter in c files.
      - Problems caused by assuming "char" is signed.
        cash.in: building -signed the rules regression test fails as described
          in FAQ_QNX4.  If CHAR_MAX is "255U" then ((signed char)CHAR_MAX) is -1.
        postmaster.c: random number regression test failed without this change.
      - Some generic build issues and warning message cleanup.
      
      David Kaelbling
      a47e20b0
  17. 12 Apr, 2000 1 commit
  18. 19 Mar, 2000 1 commit
  19. 15 Jan, 2000 1 commit
  20. 17 Jul, 1999 1 commit
  21. 16 Jul, 1999 1 commit
  22. 15 Jul, 1999 1 commit
  23. 14 Jul, 1999 1 commit
  24. 25 May, 1999 1 commit
  25. 12 Oct, 1998 1 commit
  26. 01 Sep, 1998 2 commits
  27. 15 Jun, 1998 1 commit
  28. 02 Mar, 1998 1 commit
  29. 26 Feb, 1998 1 commit
  30. 07 Jan, 1998 1 commit
  31. 05 Jan, 1998 2 commits
  32. 25 Oct, 1997 1 commit
  33. 03 Oct, 1997 1 commit
  34. 20 Sep, 1997 1 commit
  35. 18 Sep, 1997 1 commit
  36. 13 Sep, 1997 2 commits