- 21 Aug, 1997 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
Change pg_attribute.attnvals to float4, change #ifdef 0 to #if 0, fix aix call to strNcpy, fix pg_super_user_id in pg_dumpall, change pg_database.dtadba from oid to int4.
-
Vadim B. Mikheev authored
-
- 19 Aug, 1997 1 commit
-
-
Vadim B. Mikheev authored
-
- 14 Jan, 1997 1 commit
-
-
Bruce Momjian authored
-
- 10 Jan, 1997 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
At least the first two should be fixed before the final release of 6.0. 1) There is a mismatch between the type declared in the catalog for the input/output attributes of pg_type and the actual type of values stored in the table. The type of typinput, typoutput, typsend and typreceive are declared oid (26) while the values are regproc (24). The error was there also in previous versions but nobody noticed it until an Assert has been added in ExecEvalVar. The effect is that it is now impossible to replace the typoutput of existing data types with new procs. 2) The identd hba fails after the first time because the data read from the identd socket is not zero-terminated and strlen reports an incorrect length if the stack contains garbage, which usually happens after the first connection has been made. 3) The new initdb wants to create itself the data directory. This implies that the parent directory must be writable by postgres and this may not always be desirable. A better solution would be to allow the directory to be created by root and then filled by initdb. It would also nice to have some reasonable default for PGLIB and PGDATA like the previous version did. This applies also to the postmaster executable.
-
- 13 Nov, 1996 1 commit
-
-
Marc G. Fournier authored
Changes: * Unique index capability works using the syntax 'create unique index'. * Duplicate OID's in the system tables are removed. I put little scripts called 'duplicate_oids' and 'find_oid' in include/catalog that help to find and remove duplicate OID's. I also moved 'unused_oids' from backend/catalog to include/catalog, since it has to be in the same directory as the include files in order to work. * The backend tries converting the name of a function or aggregate to all lowercase if the original name given doesn't work (mostly for compatibility with ODBC). * You can 'SELECT NULL' to your heart's content. * I put my _bt_updateitem fix in instead, which uses _bt_insertonpg so that even if the new key is so big that the page has to be split, everything still works. * All literal references to system catalog OID's have been replaced with references to define'd constants from the catalog header files. * I added a couple of node copy functions. I think this was a preliminary attempt to get rules to work.
-
- 01 Nov, 1996 1 commit
-
-
Marc G. Fournier authored
access/tupdesc.h catalog/pg_attribute.h nodes/pg_list.h nodes/nodes.h access/attnum.h
-
- 31 Oct, 1996 1 commit
-
-
Marc G. Fournier authored
#include "postgres.h" #include "c.h"
-
- 28 Aug, 1996 1 commit
-
-
Marc G. Fournier authored
- centralizing to simplify the -I's required to compile
-
- 24 Aug, 1996 1 commit
-
-
Marc G. Fournier authored
In a catalog class that has a "name" type attribute, UPDATEing of an instance of that class may destroy all of the attributes of that instance that are stored as or after the "name" attribute. This is caused by the alignment value of the "name" type being set to "double" in Class pg_type, but "integer" in Class pg_attribute. Postgres constructs a tuple using double alignment, but interprets it using integer alignment. The fix is to change the alignment to integer in pg_type. Note that this corrects the problem for new Postgres systems. Existing databases already contain the error and it can't easily be repaired because this very bug prevents updating the class that contains it. -- Bryan Henderson Phone 408-227-6803 San Jose, California
-
- 21 Aug, 1996 1 commit
-
-
Marc G. Fournier authored
When you try to do any UPDATE of the catalog class pg_class, such as to change ownership of a class, the backend crashes. This is really two serial bugs: 1) there is a hardcoded copy of the schema of pg_class in the postgres program, and it doesn't match the actual class that initdb creates in the database; 2) Parts of postgres determine whether to pass an attribute value by value or by reference based on the attbyval attribute of the attribute in class pg_attribute. Other parts of postgres have it hardcoded. For the relacl[] attribute in class pg_class, attbyval does not match the hardcoded expectation. The fix is to correct the hardcoded schema for pg_attribute and to change the fetchatt macro so it ignores attbyval for all variable length attributes. The fix also adds a bunch of logic documentation and extends genbki.sh so it allows source files to contain such documentation. -- Bryan Henderson Phone 408-227-6803 San Jose, California
-
- 09 Jul, 1996 1 commit
-
-
Marc G. Fournier authored
-