1. 16 12月, 1999 1 次提交
  2. 12 12月, 1999 2 次提交
    • B
      I'm in TODO mood today ... · cb00b7fa
      Bruce Momjian 提交于
      * Document/trigger/rule so changes to pg_shadow recreate pg_pwd
      
      I did it with a trigger and it seems to work like a charm. The function
      that already updates the file for create and alter user has been made a
      built-in "SQL" function and a trigger is created at initdb time.
      
      Comments around the pg_pwd updating function seem to be worried about
      this
      routine being called concurrently, but I really don't see a reason to
      worry about this. Verify for yourself. I guess we never had a system
      trigger before, so treat this with care, and feel free to adjust the
      nomenclature as well.
      
      --
      Peter Eisentraut                  Sernanders väg 10:115
      cb00b7fa
    • B
      Fix for psql from Peter. · 1ff0a475
      Bruce Momjian 提交于
      1ff0a475
  3. 11 12月, 1999 3 次提交
  4. 10 12月, 1999 2 次提交
  5. 09 12月, 1999 1 次提交
  6. 08 12月, 1999 3 次提交
  7. 06 12月, 1999 7 次提交
  8. 04 12月, 1999 1 次提交
  9. 30 11月, 1999 1 次提交
  10. 29 11月, 1999 1 次提交
  11. 28 11月, 1999 2 次提交
  12. 27 11月, 1999 1 次提交
  13. 26 11月, 1999 2 次提交
    • B
      Fix missing prototype psql warning. · 09f185a0
      Bruce Momjian 提交于
      09f185a0
    • B
      * Includes tab completion. It's not magic, but it's very cool. At any · 78bc83fe
      Bruce Momjian 提交于
      rate
        it's better than what used to be there.
      
      * Does proper SQL "host variable" substitution as pointed out by Andreas
        Zeugwetter (thanks): select * from :foo; Also some changes in how ':'
        and ';' are treated (escape with \ to send to backend). This does
      _not_
        affect the '::' cast operator, but perhaps others that contain : or ;
        (but there are none right now).
      
      * To show description with a <something> listing, append '?' to command
        name, e.g., \df?. This seemed to be the convenient and logical
      solution.
        Or append a '+' to see more useless information, e.g., \df+.
      
      * Fixed fflush()'ing bug pointed out by Jan during the regression test
        discussion.
      
      * Added LastOid variable. This ought to take care of TODO item "Add a
        function to return the last inserted oid, for use in psql scripts"
        (under CLIENTS)
        E.g.,
      insert into foo values(...);
      insert into bar values(..., :LastOid);
      \echo $LastOid
      
      * \d command shows constraints, rules, and triggers defined on the table
        (in addition to indices)
      
      * Various fixes, optimizations, corrections
      
      * Documentation update as well
      
      
      Note: This now requires snprintf(), which, if necessary, is taken from
      src/backend/port. This is certainly a little weird, but it should
      suffice
      until a source tree cleanup is done.
      
      Enjoy.
      
      --
      Peter Eisentraut                  Sernanders väg 10:115
      78bc83fe
  14. 23 11月, 1999 1 次提交
  15. 21 11月, 1999 1 次提交
    • T
      Change backend-side COPY to write files with permissions 644 not 666 · d8ba3dfb
      Tom Lane 提交于
      (whoever thought world-writable files were a good default????).  Modify
      the pg_pwd code so that pg_pwd is created with 600 permissions.  Modify
      initdb so that permissions on a pre-existing PGDATA directory are not
      blindly accepted: if the dir is already there, it does chmod go-rwx
      to be sure that the permissions are OK and the dir actually is owned
      by postgres.
      d8ba3dfb
  16. 19 11月, 1999 1 次提交
  17. 14 11月, 1999 1 次提交
  18. 13 11月, 1999 1 次提交
  19. 11 11月, 1999 1 次提交
    • B
      In the spirit of TODO item · 2a24ec6f
      Bruce Momjian 提交于
      * Add use of 'const' for varibles in source tree
      (which is misspelled, btw.)
      I went through the front-end libpq code and did so. This affects in
      particular the various accessor functions (such as PQdb() and
      PQgetvalue()) as well as, by necessity, the internal helpers they use.
      
      I have been really thorough in that regard, perhaps some people will find
      it annoying that things like
      char * foo = PQgetvalue(res, 0, 0)
      will generate a warning. On the other hand it _should_ generate one. This
      is no real compatibility break, although a few clients will have to be
      fixed to suppress warnings. (Which again would be in the spirit of the
      above TODO.)
      
      In addition I replaced some int's by size_t's and removed some warnings
      (and generated some new ones -- grmpf!). Also I rewrote PQoidStatus (so it
      actually honors the const!) and supplied a new function PQoidValue that
      returns a proper Oid type. This is only front-end stuff, none of the
      communicaton stuff was touched.
      
      
      The psql patch also adds some new consts to honor the new libpq situation,
      as well as fixes a fatal condition that resulted when using the -V
      (--version) option and there is no database listening.
      
      
      So, to summarize, the psql you should definitely put in (with or without
      the libpq). If you think I went too far with the const-mania in libpq, let
      me know and I'll make adjustments. If you approve it, I will also update
      the docs.
      
              -Peter
      
      --
      Peter Eisentraut                  Sernanders vaeg 10:115
      2a24ec6f
  20. 10 11月, 1999 1 次提交
  21. 08 11月, 1999 2 次提交
  22. 07 11月, 1999 2 次提交
  23. 06 11月, 1999 1 次提交
  24. 05 11月, 1999 1 次提交