- 22 Jul, 2000 1 commit
-
-
Tom Lane authored
-
- 17 Jul, 2000 1 commit
-
-
Tom Lane authored
There's now only one transition value and transition function. NULL handling in aggregates is a lot cleaner. Also, use Numeric accumulators instead of integer accumulators for sum/avg on integer datatypes --- this avoids overflow at the cost of being a little slower. Implement VARIANCE() and STDDEV() aggregates in the standard backend. Also, enable new LIKE selectivity estimators by default. Unrelated change, but as long as I had to force initdb anyway...
-
- 05 Jul, 2000 1 commit
-
-
Tom Lane authored
one of updating the whole text datatype, but there are so dang many calls of these two routines that it seems worth a separate commit.
-
- 28 Jun, 2000 1 commit
-
-
Tom Lane authored
for details). It doesn't really do that much yet, since there are no short-term memory contexts in the executor, but the infrastructure is in place and long-term contexts are handled reasonably. A few long- standing bugs have been fixed, such as 'VACUUM; anything' in a single query string crashing. Also, out-of-memory is now considered a recoverable ERROR, not FATAL. Eliminate a large amount of crufty, now-dead code in and around memory management. Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and backend startup.
-
- 25 Jun, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 12 Jun, 2000 1 commit
-
-
Bruce Momjian authored
-
- 09 Jun, 2000 2 commits
-
-
Bruce Momjian authored
more restriction for fretful users. The current PG allow define only NO-CREATE-DB and NO-CREATE-USER restriction, but for some users I need NO-CREATE-TABLE and NO-LOCK-TABLE. This patch add to current code NOCREATETABLE and NOLOCKTABLE feature: CREATE USER username [ WITH [ SYSID uid ] [ PASSWORD 'password' ] ] [ CREATEDB | NOCREATEDB ] [ CREATEUSER | NOCREATEUSER ] -> [ CREATETABLE | NOCREATETABLE ] [ LOCKTABLE | NOLOCKTABLE ] ...etc. If CREATETABLE or LOCKTABLE is not specific in CREATE USER command, as default is set CREATETABLE or LOCKTABLE (true). A user with NOCREATETABLE restriction can't call CREATE TABLE or SELECT INTO commands, only create temp table is allow for him. Karel
-
Tom Lane authored
-
- 02 Jun, 2000 1 commit
-
-
Tom Lane authored
it will close VFDs if necessary to surmount ENFILE or EMFILE failures. Make use of this in md.c, xlog.c, and user.c routines that were formerly vulnerable to these failures. In particular, this should handle failures of mdblindwrt() that have been observed under heavy load conditions. (By golly, every other process on the system may crash after Postgres eats up all the kernel FDs, but Postgres will keep going!)
-
- 30 May, 2000 1 commit
-
-
Bruce Momjian authored
-
- 29 May, 2000 1 commit
-
-
Tom Lane authored
CurrentTriggerData is history.
-
- 28 May, 2000 1 commit
-
-
Tom Lane authored
key call sites are changed, but most called functions are still oldstyle. An exception is that the PL managers are updated (so, for example, NULL handling now behaves as expected in plperl and plpgsql functions). NOTE initdb is forced due to added column in pg_proc.
-
- 04 May, 2000 1 commit
-
-
Tom Lane authored
failure of rename() call.
-
- 12 Apr, 2000 1 commit
-
-
Bruce Momjian authored
-
- 15 Mar, 2000 1 commit
-
-
Tom Lane authored
-
- 15 Feb, 2000 1 commit
-
-
Tom Lane authored
-
- 26 Jan, 2000 1 commit
-
-
Bruce Momjian authored
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
-
- 14 Jan, 2000 1 commit
-
-
Peter Eisentraut authored
* Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
-
- 21 Dec, 1999 1 commit
-
-
Jan Wieck authored
Jan
-
- 20 Dec, 1999 1 commit
-
-
Tom Lane authored
-
- 16 Dec, 1999 1 commit
-
-
Bruce Momjian authored
didn't have time for documentation yet, but I'll write some. There are still some things to work out what happens when you alter or drop users, but the group stuff in and by itself is done. -- Peter Eisentraut Sernanders väg 10:115
-
- 14 Dec, 1999 3 commits
-
-
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
-
Bruce Momjian authored
triggered function now returns the right datatype. -- Peter Eisentraut Sernanders väg 10:115
-
Bruce Momjian authored
anywhere from zero to two TODO items. * Allow flag to control COPY input/output of NULLs I got this: COPY table .... [ WITH NULL AS 'string' ] which does what you'd expect. The default is \N, otherwise you can use empty strings, etc. On Copy In this acts like a filter: every data item that looks like 'string' becomes a NULL. Pretty straightforward. This also seems to be related to * Make postgres user have a password by default If I recall this discussion correctly, the problem was actually that the default password for the postgres (or any) user is in fact "\N", because of the way copy is used. With this change, the file pg_pwd is copied out with nulls as empty strings, so if someone doesn't have a password, the password is just '', which one would expect from a new account. I don't think anyone really wants a hard-coded default password. Peter Eisentraut Sernanders väg 10:115
-
- 12 Dec, 1999 1 commit
-
-
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
-
- 30 Nov, 1999 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
This one should work much better than the one I sent in previously. The functionality is the same, but the patch was missing one file resulting in the compilation failing. The docs also received a minor fix. Peter Eisentraut Sernanders väg 10:115
-
- 24 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-
- 22 Nov, 1999 1 commit
-
-
Bruce Momjian authored
Make all system indexes unique. Make all cache loads use system indexes. Rename *rel to *relid in inheritance tables. Rename cache names to be clearer.
-
- 21 Nov, 1999 1 commit
-
-
Tom Lane authored
(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.
-
- 27 Sep, 1999 1 commit
-
-
Bruce Momjian authored
-
- 18 Sep, 1999 1 commit
-
-
Tom Lane authored
additional argument specifying the kind of lock to acquire/release (or 'NoLock' to do no lock processing). Ensure that all relations are locked with some appropriate lock level before being examined --- this ensures that relevant shared-inval messages have been processed and should prevent problems caused by concurrent VACUUM. Fix several bugs having to do with mismatched increment/decrement of relation ref count and mismatched heap_open/close (which amounts to the same thing). A bogus ref count on a relation doesn't matter much *unless* a SI Inval message happens to arrive at the wrong time, which is probably why we got away with this sloppiness for so long. Repair missing grab of AccessExclusiveLock in DROP TABLE, ALTER/RENAME TABLE, etc, as noted by Hiroshi. Recommend 'make clean all' after pulling this update; I modified the Relation struct layout slightly. Will post further discussion to pghackers list shortly.
-
- 30 Jul, 1999 1 commit
-
-
Bruce Momjian authored
update temp tables with this setting.
-
- 17 Jul, 1999 1 commit
-
-
Bruce Momjian authored
-
- 16 Jul, 1999 1 commit
-
-
Bruce Momjian authored
-
- 15 Jul, 1999 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 25 May, 1999 1 commit
-
-
Bruce Momjian authored
-
- 02 Apr, 1999 1 commit
-
-
Tom Lane authored
parameters in CREATE USER.
-
- 16 Mar, 1999 1 commit
-
-
Bruce Momjian authored
-