- 04 Feb, 2000 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 03 Feb, 2000 1 commit
-
-
Bruce Momjian authored
-
- 29 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 28 Jan, 2000 4 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 24 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 23 Jan, 2000 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 22 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 21 Jan, 2000 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 17 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 16 Jan, 2000 4 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 15 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 14 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 13 Jan, 2000 7 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 11 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 10 Jan, 2000 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 14 Dec, 1999 1 commit
-
-
Bruce Momjian authored
triggered > function now returns the right datatype. Oops, I got crossed up with Jan's improvements. Ignore this. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala
-
- 12 Dec, 1999 2 commits
-
-
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
-
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
-
- 11 Dec, 1999 1 commit
-
-
Bruce Momjian authored
-
- 30 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-
- 26 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-
- 22 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-
- 14 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-