1. 28 10月, 2015 2 次提交
    • H
      Remove -Werror, replace with more specific -Wno-* options. · 0675ad72
      Heikki Linnakangas 提交于
      It's important to pay attention to compiler warnings, but -Werror isn't
      buying us much at the moment. Firstly, there are a lot of warnings on modern
      versions of gcc. I have to pass: "-Wno-error=unused-but-set-variable
      -Wno-error=enum-compare -Wno-error=address -Wno-error=maybe-uninitialized"
      to make it compile. More important than erroring out on warnings is to make
      sure there are no warnings to begin with. Once we get to that state, any
      warnings will stick out like sore thumb anyway, and you won't need -Werror
      to make them more annoying.
      
      We have a long way until we are 100% warning free, but most of the warnings
      come from upstream code. They have been fixed in later versions of
      PostgreSQL, so they will go away as we merge with upstream.
      0675ad72
    • I
      Import Greenplum source code. · 6b0e52be
      Initial Greenplum code dump 提交于
      6b0e52be
  2. 09 10月, 2006 1 次提交
  3. 04 10月, 2006 1 次提交
    • T
      Switch over to using our own qsort() all the time, as has been proposed · 6edd2b4a
      Tom Lane 提交于
      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
  4. 19 9月, 2006 1 次提交
  5. 11 9月, 2006 2 次提交
  6. 09 9月, 2006 1 次提交
  7. 23 8月, 2006 1 次提交
  8. 25 7月, 2006 1 次提交
  9. 22 7月, 2006 1 次提交
  10. 20 7月, 2006 1 次提交
  11. 20 4月, 2006 1 次提交
    • T
      Remove use of lorder and tsort while building static libraries. There's · 04ca4caa
      Tom Lane 提交于
      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
  12. 12 2月, 2006 1 次提交
  13. 28 9月, 2005 1 次提交
    • T
      Fix problems with PGXS builds against an installation tree that was · 4fc935a5
      Tom Lane 提交于
      relocated after installation.  We can't trust the installation paths
      inserted into Makefile.global by configure, so instead we must get the
      paths from pg_config.  This requires extending pg_config to support all
      the separately-configurable path names, but that was on TODO anyway.
      4fc935a5
  14. 03 8月, 2005 1 次提交
    • T
      Clean up CREATE DATABASE processing to make it more robust and get rid · 558730ac
      Tom Lane 提交于
      of special case for Windows port.  Put a PG_TRY around most of createdb()
      to ensure that we remove copied subdirectories on failure, even if the
      failure happens while creating the pg_database row.  (I think this explains
      Oliver Siegmar's recent report.)  Having done that, there's no need for
      the fragile assumption that copydir() mustn't ereport(ERROR), so simplify
      its API.  Eliminate the old code that used system("cp ...") to copy
      subdirectories, in favor of using copydir() on all platforms.  This not
      only should allow much better error reporting, but allows us to fsync
      the created files before trusting that the copy has succeeded.
      558730ac
  15. 28 7月, 2005 1 次提交
  16. 07 7月, 2005 1 次提交
  17. 06 7月, 2005 1 次提交
  18. 04 7月, 2005 1 次提交
  19. 18 5月, 2005 1 次提交
  20. 26 3月, 2005 2 次提交
  21. 25 3月, 2005 2 次提交
  22. 27 1月, 2005 1 次提交
  23. 19 12月, 2004 1 次提交
  24. 17 12月, 2004 2 次提交
  25. 19 11月, 2004 1 次提交
  26. 20 10月, 2004 1 次提交
    • N
      When using GCC, change the default CFLAGS to: · 857e210e
      Neil Conway 提交于
        -O2 -Wall -Wmissing-prototypes -Wpointer-arith
      
      Check whether the version of GCC we are using supports any of:
      
        -Wdeclaration-after-statement
        -Wendif-labels
        -Wold-style-definition
      
      And add the supported flags to CFLAGS.
      857e210e
  27. 16 10月, 2004 1 次提交
    • B
      The previous build rules caused each binary to be re-linked on every · db9e2fd0
      Bruce Momjian 提交于
      "make", even if nothing had changed. With this patch, it's only relinked
      if it's actually updated.
      
      //Magnus
      
      PS. Yes, the old buildrule for the .rc file is still needed, as it's
      used by pgevent.rc (or any other binary in the future that would need
      it's own .rc file)
      
      Magnus Hagander
      db9e2fd0
  28. 15 10月, 2004 1 次提交
    • B
      > This lets you do something like: · 4d94e99b
      Bruce Momjian 提交于
      >
      >    ./configure LDFLAGS=-static-libgcc LDFLAGS_SL=-static-libgcc
      >
      > to produce binaries that do not depend on libgcc_s.so at all.
      
      Oliver Jowett
      4d94e99b
  29. 12 10月, 2004 1 次提交
    • T
      Another try at making plpython autoconfiguration work correctly. Use a · 669ca7af
      Tom Lane 提交于
      -L spec rather than assuming libpython is in the standard search path
      (this returns to the way 7.4 did it).  But check the distutils output
      to see if it looks like Python has built a shared library, and if so
      link with that instead of the probably-not-shared library found in
      configdir.
      669ca7af
  30. 06 10月, 2004 4 次提交
  31. 01 10月, 2004 1 次提交
  32. 18 9月, 2004 1 次提交