1. 17 Dec, 1999 3 commits
    • Bruce Momjian's avatar
      Reverse out nextval patch. · 21992ed1
      Bruce Momjian authored
      21992ed1
    • Bruce Momjian's avatar
      initdb.sh fix from Peter. · ac00256c
      Bruce Momjian authored
      ac00256c
    • Bruce Momjian's avatar
      This is my -- hopefully sufficiently portable -- attempt at cleaning out · 83bad7c0
      Bruce Momjian authored
      initdb. No more obscure dependencies on environment variables or paths.
      It
      now finds the templates and the right postgres itself (with cmd line
      options as fallback). It also no longer depends on $USER (su safe), and
      doesn't advertise that --username allows you to install the db as a
      different user, since that doesn't work anyway. Also, recovery and
      cleanup
      on all errors. Consistent options, clearer documentation.
      
      Please take a look at this and adopt it if you feel it's safe enough. I
      have simulated all the stupid circumstances I could think of, but you
      never know with shell scripts.
      
      Oh yeah, you can give the postgres user a default password now.
      
      --
      Peter Eisentraut                  Sernanders väg 10:115
      83bad7c0
  2. 16 Dec, 1999 10 commits
  3. 14 Dec, 1999 5 commits
  4. 13 Dec, 1999 4 commits
  5. 12 Dec, 1999 3 commits
    • Tom Lane's avatar
      efb36d2b
    • Bruce Momjian's avatar
      I'm in TODO mood today ... · cb00b7fa
      Bruce Momjian authored
      * 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
    • Bruce Momjian's avatar
      Meanwhile, database names with single quotes in names don't work very well · 11023eb1
      Bruce Momjian authored
      at all, and because of shell quoting rules this can't be fixed, so I put
      in error messages to that end.
      
      Also, calling create or drop database in a transaction block is not so
      good either, because the file system mysteriously refuses to roll back rm
      calls on transaction aborts. :) So I put in checks to see if a transaction
      is in progress and signal an error.
      
      Also I put the whole call in a transaction of its own to be able to roll
      back changes to pg_database in case the file system operations fail.
      
      The alternative location issues I posted recently were untouched, awaiting
      the outcome of that discussion. Other than that, this should be much more
      fool-proof now.
      
      The docs I cleaned up as well.
      
      Peter Eisentraut                  Sernanders väg 10:115
      11023eb1
  6. 11 Dec, 1999 4 commits
  7. 10 Dec, 1999 11 commits