- 26 8月, 1998 5 次提交
-
-
由 Marc G. Fournier 提交于
From: Massimo Dal Zotto <dz@cs.unitn.it> > pqpacket.patch > > fixed indentation.
-
由 Marc G. Fournier 提交于
From: Massimo Dal Zotto <dz@cs.unitn.it> lock.patch I have rewritten lock.c cleaning up the code and adding better assert checking I have also added some fields to the lock and xid tags for better support of user locks. There is also a new function which returns an array of pids owning a lock. I'm using this code from over six months and it works fine.
-
由 Marc G. Fournier 提交于
From: Massimo Dal Zotto <dz@cs.unitn.it> config.patch remove old defines no more used in the code.
-
由 Marc G. Fournier 提交于
From: Massimo Dal Zotto <dz@cs.unitn.it> assert.patch adds a switch to turn on/off the assert checking if enabled at compile time. You can now compile postgres with assert checking and disable it at runtime in a production environment.
-
由 Bruce Momjian 提交于
(Mark or Bruce?) It fixes a problem when cpp gives a warning when precompiling /dev/null like: "/dev/null", line 1: 1506-229 (W) File is empty. This leads to a hangup when doing the description load during initdb, since stderr also ends up in the global1.description and local1_template1.description stderr has to be redirected to /dev/null: Andreas Zeugswetter
-
- 25 8月, 1998 18 次提交
-
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
statements: - the table definition with a default clause referencing the sequence; - a CREATE SEQUENCE statement; - a UNIQUE constraint, which expands into a CREATE INDEX statement. This is not a perfect solution, since the sequence will remain even if the table is dropped. Also, there is no absolute protection on updating the sequence column.
-
由 Thomas G. Lockhart 提交于
is_sequence in the ColumnDef structure.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Had too many in some cases because there was already a routine taking care of it.
-
由 Thomas G. Lockhart 提交于
Formerly came just after early exit from loop for command nodes, so missed some cases.
-
由 Marc G. Fournier 提交于
Add nextstep to similar template file
-
由 Marc G. Fournier 提交于
re-integrate nextstep dynloader functionality From: Jacek Lasecki <jacek@sound.eti.pg.gda.pl>
-
由 Marc G. Fournier 提交于
From: Michael Meskes <meskes@online-club.de> + + 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 +
-
由 Marc G. Fournier 提交于
From: Michael Meskes <meskes@online-club.de> + + 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 +
-
由 Marc G. Fournier 提交于
From: Michael Meskes <meskes@online-club.de> + + 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 +
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
rewrite system. Restructure parse_target to make it easier to understand.
-
由 Bruce Momjian 提交于
int64 fix
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 24 8月, 1998 12 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
[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
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-
- 23 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 8月, 1998 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
test isn't that complete up to now, but I think it shows enough of the capabilities of the module. The Makefile assumes it is located in a directory under pgsql/src/pl. Since it includes Makefile.global and Makefile.port and doesn't use any own compiler/linker calls, it should build on most of our supported platforms (I only tested under Linux up to now). It requires flex and bison I think. Maybe we should ship prepared gram.c etc. like for the main parser too? Jan
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-