aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Clean up double-quotes around column and table names.Thomas G. Lockhart1998-08-25
| | | | | Had too many in some cases because there was already a routine taking care of it.
* Move debugging printout of the query tree to print for all cases.Thomas G. Lockhart1998-08-25
| | | | | Formerly came just after early exit from loop for command nodes, so missed some cases.
* Add nextstep to similar template fileMarc G. Fournier1998-08-25
|
* re-integrate nextstep dynloader functionalityMarc G. Fournier1998-08-25
| | | | From: Jacek Lasecki <jacek@sound.eti.pg.gda.pl>
* From: Michael Meskes <meskes@online-club.de>Marc G. Fournier1998-08-25
| | | | | | | | | | | | | | | | | | | | | | | + + Fri Aug 14 12:44:21 CEST 1998 + + - Added EXEC SQL DEFINE statement + - Set version to 2.4.0 + + Tue Aug 18 09:24:15 CEST 1998 + + - Removed keyword IS from DEFINE statement + - Added latest changes from gram.y + - Removed duplicate symbols from preproc.y + - Initialize sqlca structure + - Added check for connection to ecpglib + - Set version to 2.4.1 + + Thu Aug 20 15:31:29 CEST 1998 + + - Cleaned up memory allocation in ecpglib.c + - Set library version to 2.6 +
* From: Michael Meskes <meskes@online-club.de>Marc G. Fournier1998-08-25
| | | | | | | | | | | | | | | | | | | | | | | + + Fri Aug 14 12:44:21 CEST 1998 + + - Added EXEC SQL DEFINE statement + - Set version to 2.4.0 + + Tue Aug 18 09:24:15 CEST 1998 + + - Removed keyword IS from DEFINE statement + - Added latest changes from gram.y + - Removed duplicate symbols from preproc.y + - Initialize sqlca structure + - Added check for connection to ecpglib + - Set version to 2.4.1 + + Thu Aug 20 15:31:29 CEST 1998 + + - Cleaned up memory allocation in ecpglib.c + - Set library version to 2.6 +
* From: Michael Meskes <meskes@online-club.de>Marc G. Fournier1998-08-25
| | | | | | | | | | | | | | | | | | | | | | | + + Fri Aug 14 12:44:21 CEST 1998 + + - Added EXEC SQL DEFINE statement + - Set version to 2.4.0 + + Tue Aug 18 09:24:15 CEST 1998 + + - Removed keyword IS from DEFINE statement + - Added latest changes from gram.y + - Removed duplicate symbols from preproc.y + - Initialize sqlca structure + - Added check for connection to ecpglib + - Set version to 2.4.1 + + Thu Aug 20 15:31:29 CEST 1998 + + - Cleaned up memory allocation in ecpglib.c + - Set library version to 2.6 +
* >Applied.Bruce Momjian1998-08-25
| | | | | | | | Thanks. But patches for src/backend/catalog/Makefile seems missing in the current source tree. Please apply attached patches. It also includes some corrections to src/backend/util/mb/wchar.c. -- Tatsuo Ishii t-ishii@sra.co.jp
* Cleanup of target file.Bruce Momjian1998-08-25
|
* Make sure resdomno for update/insert match attribute number forBruce Momjian1998-08-25
| | | | | rewrite system. Restructure parse_target to make it easier to understand.
* int64 fixBruce Momjian1998-08-25
|
* move plpgsqlBruce Momjian1998-08-24
|
* move plpgsql to src/pl for Jan.Bruce Momjian1998-08-24
|
* Fix bootstrap so it properly defines alignment of attributes.Bruce Momjian1998-08-24
|
* autoconfBruce Momjian1998-08-24
|
* LONG_LONG_64 fix.Bruce Momjian1998-08-24
|
* autoconfBruce Momjian1998-08-24
|
* I have found a minor problem with current configure.in.Bruce Momjian1998-08-24
| | | | | | | | | | | | | | | | | [AC_MSG_RESULT(yes) AC_DEFINE(HAVE_LONG_INT_64)], this line produces something like: echo "$ac_t""yes" 1>&6 cat >> confdefs.h <<\EOF and would append garbage "yes cat" to confdefs.h. Of course the result confdefs.h is not syntactically correct therefore following tests using confdefs.h would all fail. To avoid the problem, we could switch the order of AC_MSG_RESULT and AC_DEFINE (see attached patch). This happend on my LinuxPPC box. Tatsuo Ishii t-ishii@sra.co.jp
* man pages cleanupBruce Momjian1998-08-24
|
* OLD has to return CURRENT for now, Jan.Bruce Momjian1998-08-24
|
* This is the final state of the rule system for 6.4 after theBruce Momjian1998-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | patch is applied: Rewrite rules on relation level work fine now. Event qualifications on insert/update/delete rules work fine now. I added the new keyword OLD to reference the CURRENT tuple. CURRENT will be removed in 6.5. Update rules can reference NEW and OLD in the rule qualification and the actions. Insert/update/delete rules on views can be established to let them behave like real tables. For insert/update/delete rules multiple actions are supported now. The actions can also be surrounded by parantheses to make psql happy. Multiple actions are required if update to a view requires updates to multiple tables. Regular users are permitted to create/drop rules on tables they have RULE permissions for (DefineQueryRewrite() is now able to get around the access restrictions on pg_rewrite). This enables view creation for regular users too. This required an extra boolean parameter to pg_parse_and_plan() that tells to set skipAcl on all rangetable entries of the resulting queries. There is a new function pg_exec_query_acl_override() that could be used by backend utilities to use this facility. All rule actions (not only views) inherit the permissions of the event relations owner. Sample: User A creates tables T1 and T2, creates rules that log INSERT/UPDATE/DELETE on T1 in T2 (like in the regression tests for rules I created) and grants ALL but RULE on T1 to user B. User B can now fully access T1 and the logging happens in T2. But user B cannot access T2 at all, only the rule actions can. And due to missing RULE permissions on T1, user B cannot disable logging. Rules on the attribute level are disabled (they don't work properly and since regular users are now permitted to create rules I decided to disable them). Rules on select must have exactly one action that is a select (so select rules must be a view definition). UPDATE NEW/OLD rules are disabled (still broken, but triggers can do it). There are two new system views (pg_rule and pg_view) that show the definition of the rules or views so the db admin can see what the users do. They use two new functions pg_get_ruledef() and pg_get_viewdef() that are builtins. The functions pg_get_ruledef() and pg_get_viewdef() could be used to implement rule and view support in pg_dump. PostgreSQL is now the only database system I know, that has rewrite rules on the query level. All others (where I found a rule statement at all) use stored database procedures or the like (triggers as we call them) for active rules (as some call them). Future of the rule system: The now disabled parts of the rule system (attribute level, multiple actions on select and update new stuff) require a complete new rewrite handler from scratch. The old one is too badly wired up. After 6.4 I'll start to work on a new rewrite handler, that fully supports the attribute level rules, multiple actions on select and update new. This will be available for 6.5 so we get full rewrite rule capabilities. Jan
* Compile ecpg by default.Bruce Momjian1998-08-24
|
* just that the regression tests for rules work, please applyBruce Momjian1998-08-24
| | | | | | | | | | | | | | | | | | | the following to regress/sql/tests. If applying by hand note that the setup_... must run before the run_... (that I splitted these two was due to the errors that occured when creating rules and using them then in the same session - I'll post another fix for this later). BTW: the regression tests sanity_checks and alter_table fail now due to the remove of some indices and the oidint4 and oidname types. At least expectes should be set to the current results. Thanks. Jan
* o note that now pg_database has a new attribuite "encoding" evenBruce Momjian1998-08-24
| | | | | | | | | | | | | | | | | | | | | | if MULTIBYTE is not enabled. So be sure to run initdb. o these patches are made against the latest source tree (after Bruce's massive patch, I think) BTW, I noticed that after running regression, the oid field of pg_type seems disappeared. regression=> select oid from pg_type; ERROR: attribute 'oid' not found this happens after the constraints test. This occures with/without my patches. strange... o pg_database_mb.h, pg_class_mb.h, pg_attribute_mb.h are no longer used, and shoud be removed. o GetDatabaseInfo() in utils/misc/database.c removed (actually in #ifdef 0). seems nobody uses. t-ishii@sra.co.jp
* autoconfBruce Momjian1998-08-23
|
* Attached is a patch that uses autoconf to determine whether thereBruce Momjian1998-08-23
| | | | | | | | | | | | | | | is a working 64-bit-int type available. In playing around with it on my machine, I found that gcc provides perfectly fine support for "long long" arithmetic ... but sprintf() and sscanf(), which are system-supplied, don't work :-(. So the autoconf test program does a cursory test on them too. If we find that a lot of systems are like this, it might be worth the trouble to implement binary<->ASCII conversion of int64 ourselves rather than relying on sprintf/sscanf to handle the data type. regards, tom lane
* cleanupBruce Momjian1998-08-23
|
* Patch to allow createuser options from the command line.Bruce Momjian1998-08-22
|
* With the attached patch, I have verified that long (> 8char anyway)Bruce Momjian1998-08-22
| | | | | | | | | | | | | | | | | | | | | usernames and passwords work correctly in both "password" and "crypt" authorization mode. NOTE: at least on my machine, it seems that the crypt() routines ignore the part of the password beyond 8 characters, so there's no security gain from longer passwords in crypt auth mode. But they don't fail. The login-related part of psql has apparently not been touched since roughly the fall of Rome ;-). It was going through huge pushups to get around the lack of username/login parameters to PQsetdb. I don't know when PQsetdbLogin was added to libpq, but it's there now ... so I was able to rip out quite a lot of crufty code while I was at it. It's possible that there are still bogus length limits on username or password in some of the other PostgreSQL user interfaces besides psql/libpq. I will leave it to other folks to check that code. regards, tom lane
* The attached patch fixes a problem that I seem to have introducedBruce Momjian1998-08-22
| | | | | | | | | with the new support for asynchronous NOTIFY in libpgtcl. With the current sources, if the backend disconnects unexpectedly then the tcl/tk application coredumps when control next reaches the idle loop. Oops. regards, tom lane
* Here are additional patches for the UnixWare 7 port.Bruce Momjian1998-08-22
| | | | | | | | | | | | | | | | | | | Summary of changes: In pqcomm.h, use the SUN_LEN macro if it is defined to calculate the size of the sockaddr_un structure. In unixware.h, drop the use of the UNIXWARE macro. Everything can be handled with the USE_UNIVEL_CC and DISABLE_COMPLEX_MACRO macros. In s_lock.h, remove the reference to the UNIXWARE macro (see above). In the unixware template, add the YFLAGS:-d line. In various makefile templates, add (or cleanup) unixware and univel port specific information. -- Billy G. Allie
* Fix display in initdb.Bruce Momjian1998-08-21
|
* Fix for index problem that showed up in constraint test.Bruce Momjian1998-08-20
|
* update fixes.Bruce Momjian1998-08-20
|
* fix for index problem.Bruce Momjian1998-08-20
|
* Another vacuum fix.Bruce Momjian1998-08-20
|
* Fix for vacuum introduced today.Bruce Momjian1998-08-19
|
* Vacuum cleanup.Bruce Momjian1998-08-19
|
* Vacuum fix. Was modifying cache.Bruce Momjian1998-08-19
|
* Fix for vacuum updating problem.Bruce Momjian1998-08-19
|
* fix for ecpg corruptionBruce Momjian1998-08-19
|
* heap_fetch requires buffer pointer, must be released; heap_getnextBruce Momjian1998-08-19
| | | | | | | | | | | | | no longer returns buffer pointer, can be gotten from scan; descriptor; bootstrap can create multi-key indexes; pg_procname index now is multi-key index; oidint2, oidint4, oidname are gone (must be removed from regression tests); use System Cache rather than sequential scan in many places; heap_modifytuple no longer takes buffer parameter; remove unused buffer parameter in a few other functions; oid8 is not index-able; remove some use of single-character variable names; cleanup Buffer variables usage and scan descriptor looping; cleaned up allocation and freeing of tuples; 18k lines of diff;
* Fix for SNPRINTF test in configureMarc G. Fournier1998-08-19
| | | | From: Tom Lane <tgl@sss.pgh.pa.us>
* Add rule tests to regression tests...Marc G. Fournier1998-08-19
|
* From: Jan Wieck <jwieck@debis.com>Marc G. Fournier1998-08-18
| | | | | | | | | Hi, as proposed here comes the first patch for the query rewrite system. <for details, see archive dated Mon, 17 Aug 1998>
* Update the random test so it should succeed most of the time.Thomas G. Lockhart1998-08-17
| | | | | Instead of directly showing the random results, test the results for the expected behavior (range and randomness).
* Update for changes to gram.y.Thomas G. Lockhart1998-08-17
|
* Allow NOT LIKE, IN, NOT IN, BETWEEN, and NOT BETWEEN expressionsThomas G. Lockhart1998-08-17
| | | | | | | in constraint clauses. IN and NOT IN only allow constaints, not subselects. Jose' Soares' new reference docs pointed out the discrepency. Updating the docs too...
* Use the parser macro IS_BINARY_COMPATIBLE() to allow more successThomas G. Lockhart1998-08-17
| | | | | in type checking for DEFAULT contraint clauses. Could do more type coersion later...
* From: Tom Lane <tgl@sss.pgh.pa.us>To: pgsql-patches@postgreSQL.orgMarc G. Fournier1998-08-17
| | | | | | Sigh. That tweak needs a tweak --- I didn't realize that ".DEFAULT" processing ignores dependencies, at least in the version of gmake I have here (not sure if it's a bug or not). Apply this patch aftermy previous one...
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 07:44:59 +0000