- 04 Jun, 2000 1 commit
-
-
Peter Eisentraut authored
Install a default configuration file. Clean up some funny business in the config file code.
-
- 11 May, 2000 1 commit
-
-
Tom Lane authored
It's still pretty fundamentally bogus :-(. Freebie side benefit: ALTER TABLE RENAME works on indexes now.
-
- 25 Apr, 2000 1 commit
-
-
Hiroshi Inoue authored
-
- 12 Apr, 2000 1 commit
-
-
Bruce Momjian authored
-
- 04 Apr, 2000 1 commit
-
-
Tom Lane authored
would crash, due to premature invocation of SetQuerySnapshot(). Clean up problems with handling of multiple queries by splitting pg_parse_and_plan into two routines. The old code would not, for example, do the right thing with END; SELECT... submitted in one query string when it had been in transaction abort state, because it'd decide to skip planning the SELECT before it had executed the END. New arrangement is simpler and doesn't force caller to plan if only parse+rewrite is needed.
-
- 19 Feb, 2000 1 commit
-
-
Tom Lane authored
for 'const' qualifiers yet ...
-
- 18 Feb, 2000 1 commit
-
-
Hiroshi Inoue authored
-
- 29 Jan, 2000 1 commit
-
-
Peter Eisentraut authored
Initdb help correction Changed end/abort to commit/rollback and changed related notices Commented out way old printing functions in libpq Fixed a typo in alter table / alter column
-
- 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.
-
- 16 Jan, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 15 Jan, 2000 1 commit
-
-
Peter Eisentraut authored
- Prevent permissions on indexes - Instituted --enable-multibyte option and tweaked the MB build process where necessary - initdb prompts for superuser password
-
- 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.
-
- 13 Jan, 2000 1 commit
-
-
Peter Eisentraut authored
error-proof. Rearranged some old code and removed dead sections.
-
- 20 Dec, 1999 1 commit
-
-
Tom Lane authored
what a header file is for :-(
-
- 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 1 commit
-
-
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
-
- 10 Dec, 1999 1 commit
-
-
Bruce Momjian authored
-
- 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.
-
- 26 Oct, 1999 1 commit
-
-
Bruce Momjian authored
The following patch extends the COMMENT ON functionality to the rest of the database objects beyond just tables, columns, and views. The grammer of the COMMENT ON statement now looks like: COMMENT ON [ [ DATABASE | INDEX | RULE | SEQUENCE | TABLE | TYPE | VIEW ] <objname> | COLUMN <relation>.<attribute> | AGGREGATE <aggname> <aggtype> | FUNCTION <funcname> (arg1, arg2, ...) | OPERATOR <op> (leftoperand_typ rightoperand_typ) | TRIGGER <triggername> ON relname> Mike Mascari (mascarim@yahoo.com)
-
- 15 Oct, 1999 1 commit
-
-
Bruce Momjian authored
>From the ORACLE 7 SQL Language Reference Manual: ----------------------------------------------------- COMMENT Purpose: To add a comment about a table, view, snapshot, or column into the data dictionary. Prerequisites: The table, view, or snapshot must be in your own schema or you must have COMMENT ANY TABLE system privilege. Syntax: COMMENT ON [ TABLE table ] | [ COLUMN table.column] IS 'text' You can effectively drop a comment from the database by setting it to the empty string ''. ----------------------------------------------------- Example: COMMENT ON TABLE workorders IS 'Maintains base records for workorder information'; COMMENT ON COLUMN workorders.hours IS 'Number of hours the engineer worked on the task'; to drop a comment: COMMENT ON COLUMN workorders.hours IS ''; The current patch will simply perform the insert into pg_description, as per the TODO. And, of course, when the table is dropped, any comments relating to it or any of its attributes are also dropped. I haven't looked at the ODBC source yet, but I do know from an ODBC client standpoint that the standard does support the notion of table and column comments. Hopefully the ODBC driver is already fetching these values from pg_description, but if not, it should be trivial. Hope this makes the grade, Mike Mascari (mascarim@yahoo.com)
-
- 30 Sep, 1999 1 commit
-
-
Tom Lane authored
just some cosmetic changes now, Vadim already fixed the heap_xxx calls.
-
- 29 Sep, 1999 1 commit
-
-
Jan Wieck authored
Implements the CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS commands. TODO: Generic builtin trigger procedures Automatic execution of appropriate CREATE CONSTRAINT... at CREATE TABLE Support of new trigger type in pg_dump Swapping of huge # of events to disk Jan
-
- 27 Sep, 1999 1 commit
-
-
Vadim B. Mikheev authored
It doesn't work currently but also don't break anything -:)
-
- 23 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.
-
- 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
-
- 22 May, 1999 1 commit
-
-
Tom Lane authored
kernel's error description when file is not accessible).
-
- 17 Mar, 1999 1 commit
-
-
Bruce Momjian authored
-
- 16 Mar, 1999 1 commit
-
-
Bruce Momjian authored
I have changed to call pg_exec_query_dest() instead of pg_exec_query(). Thanks. Hiroshi Inoue
-
- 25 Feb, 1999 1 commit
-
-
Bruce Momjian authored
-
- 24 Feb, 1999 1 commit
-
-
Bruce Momjian authored
Move files to deadcode.
-
- 13 Feb, 1999 1 commit
-
-
Bruce Momjian authored
-
- 26 Jan, 1999 1 commit
-
-
Marc G. Fournier authored
primary key support cleanups from D'Arcy...
-
- 21 Jan, 1999 1 commit
-
-
Bruce Momjian authored
a field was labelled as a primary key, the system automatically created a unique index on the field. This patch extends it so that the index has the indisprimary field set. You can pull a list of primary keys with the followiing select. SELECT pg_class.relname, pg_attribute.attname FROM pg_class, pg_attribute, pg_index WHERE pg_class.oid = pg_attribute.attrelid AND pg_class.oid = pg_index.indrelid AND pg_index.indkey[0] = pg_attribute.attnum AND pg_index.indisunique = 't'; There is nothing in this patch that modifies the template database to set the indisprimary attribute for system tables. Should they be changed or should we only be concerned with user tables? D'Arcy
-
- 17 Jan, 1999 1 commit
-
-
Bruce Momjian authored
-
- 18 Dec, 1998 1 commit
-
-
Vadim B. Mikheev authored
LOCK TABLE IN ... MODE ...implemented
-
- 25 Sep, 1998 1 commit
-
-
Thomas G. Lockhart authored
to clarify actual path used.
-