1. 30 10月, 2017 1 次提交
    • A
      Retire gp_libpq_fe part 1, libpq itself · 510a20b6
      Adam Lee 提交于
          commit b0328d5631088cca5f80acc8dd85b859f062ebb0
          Author: mcdevc <a@b>
          Date:   Fri Mar 6 16:28:45 2009 -0800
      
              Separate our internal libpq front end from the client libpq library
              upgrade libpq to the latest to pick up bug fixes and support for more
              client authentication types (GSSAPI, KRB5, etc)
              Upgrade all files dependent on libpq to handle new version.
      
      Above is the initial commit of gp_libpq_fe, seems no good reasons still
      having it.
      
      Key things this PR do:
      
      1, remove the gp_libpq_fe directory.
      2, build libpq source codes into two versions, for frontend and backend,
      check the macro FRONTEND.
      3, libpq for backend still bypasses local authentication, SSL and some
      environment variables, and these are the whole differences.
      Signed-off-by: NAdam Lee <ali@pivotal.io>
      510a20b6
  2. 27 10月, 2017 1 次提交
  3. 21 10月, 2017 1 次提交
  4. 19 10月, 2017 1 次提交
  5. 30 9月, 2017 1 次提交
  6. 28 9月, 2017 1 次提交
  7. 27 9月, 2017 2 次提交
  8. 26 9月, 2017 1 次提交
  9. 23 9月, 2017 1 次提交
  10. 14 9月, 2017 2 次提交
    • D
      Use built-in JSON parser for PXF fragments (#3185) · 9f4497fd
      Daniel Gustafsson 提交于
      * Use built-in JSON parser for PXF fragments
      
      Instead of relying on a external library, use the built-in JSON
      parser in the backend for the PXF fragments parsing. Since this
      replaces the current implementation with an event-based callback
      parser, the code is more complicated, but dogfooding the parser
      that we want extension writers to use is a good thing.
      
      This removes the dependency on json-c from autoconf, and enables
      building PXF on Travis for extra coverage.
      
      * Use elog for internal errors, and ereport for user errors
      
      Internal errors where we are interested in source filename should
      use elog() which will decorate the error messages automatically
      with this information. The connection error is interesting for the
      user however, use ereport() instead there.
      9f4497fd
    • C
      71a93ade
  11. 09 9月, 2017 1 次提交
  12. 08 9月, 2017 1 次提交
    • D
      Update the README with current requirements, and fix style · f87100f4
      Daniel Gustafsson 提交于
      The README was still referencing gp-xerces even though it's no
      longer required for ORCA, so this was removed. On top of that,
      some Markdown formatting fixes, minor wordsmithing, typo fixes
      as well as some whitespace cleanup and turned URLs into links.
      f87100f4
  13. 07 9月, 2017 3 次提交
  14. 02 9月, 2017 2 次提交
  15. 31 8月, 2017 1 次提交
    • B
      Conan depends lib header location (#3107) · af3fc9b5
      Bhuvnesh 提交于
      * Change the directory location and update readme
      
      When conan is used to build the dependencies (orca & xerces) of gpdb, it
      copies the headers and libraries to the path specified in
      the imports section of the conanfile.txt.
      Changing the target copy location to /usr/local/include and
      /usr/local/lib as its the default for gpdb. In case the user
      prefers to have a different directory, they can change the location
      accordingly.
      af3fc9b5
  16. 19 7月, 2017 1 次提交
  17. 16 7月, 2017 1 次提交
  18. 14 7月, 2017 1 次提交
  19. 30 6月, 2017 2 次提交
  20. 27 6月, 2017 2 次提交
  21. 24 6月, 2017 1 次提交
  22. 13 6月, 2017 1 次提交
  23. 08 6月, 2017 1 次提交
  24. 02 6月, 2017 1 次提交
  25. 01 6月, 2017 1 次提交
  26. 31 5月, 2017 1 次提交
  27. 27 5月, 2017 1 次提交
  28. 29 4月, 2017 1 次提交
    • C
      PR Pipeline: test gpperfmon on all pull requests · 13e6686b
      C.J. Jameson 提交于
      - gpperfmon tracks a variety of queries and statistics and system
        properties and metrics in a dedicated database
      - Until recently, it hadn't been tested or built very reliably here. It
        is now part of the gpdb_master pipeline.
      - We are doing a lot of work to revitalize and provide tests for this
        feature; we plan to make many upcoming pull requests for this
        feature in different ways
      - We will look into testing this with installcheck, but for now, it is
        tested with Behave
      - Building it as part of PRs will help us get faster feedback
      - This should add negligible time to compilation: the tests themselves
        run in less than 5 minutes typically, and will be running in parallel
        with ICW
      Signed-off-by: NMarbin Tan <mtan@pivotal.io>
      13e6686b
  29. 07 4月, 2017 3 次提交
  30. 03 4月, 2017 1 次提交
    • D
      Remove unused BugBuster leftovers · 7dbaace6
      Daniel Gustafsson 提交于
      With the last remaining testsuites moved over to ICW, there is no
      longer anything left running in BugBuster. Remove the remaining
      files and BugBuster makefile integration in one big swing of the
      git rm axe. The only thing left in use was a data file which was
      referenced from ICW, move this to regress/data instead.
      7dbaace6
  31. 01 4月, 2017 1 次提交