summaryrefslogtreecommitdiff
path: root/src/backend/executor
Commit message (Collapse)AuthorAgeFilesLines
* Get rid of some long-dead code that thinks NOTIFY is passed to theTom Lane1998-10-011-41/+17
| | | | | | planner/optimizer/executor. It isn't. Besides, most of the removed code consists of comments about how it's not right.
* Clean up existing debugging print statements.Thomas G. Lockhart1998-09-253-217/+218
| | | | Modify comment blocks to insulate from pgindent.
* Allow 8-key indexes.Bruce Momjian1998-09-231-4/+4
|
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-0119-507/+504
|
* Renaming cleanup, no pgindent yet.Bruce Momjian1998-09-0117-118/+118
|
* This is the final state of the rule system for 6.4 after theBruce Momjian1998-08-242-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* fix for index problem.Bruce Momjian1998-08-201-2/+2
|
* Fix for vacuum updating problem.Bruce Momjian1998-08-191-3/+10
|
* heap_fetch requires buffer pointer, must be released; heap_getnextBruce Momjian1998-08-197-66/+45
| | | | | | | | | | | | | 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;
* Make large objects their own relkind type. Fix dups in pg_class_mbBruce Momjian1998-08-062-5/+8
| | | | files. Fix sequence creation hack for relkind type.
* OR processing cleanup.Bruce Momjian1998-08-041-23/+26
|
* Update mark/reset index code for multiple indexes, (OR code).Bruce Momjian1998-08-031-37/+33
| | | | Thanks for Vadim for fixes.
* Cleanup of OR fix.Bruce Momjian1998-08-011-2/+4
|
* Allow index use with OR clauses.Bruce Momjian1998-08-012-110/+119
|
* Use Snapshot in heap access methods.Vadim B. Mikheev1998-07-277-26/+38
|
* makeTargetEntry cleanup.Bruce Momjian1998-07-201-2/+2
|
* Cleanup makeTargetEntry and remove internal.c.Bruce Momjian1998-07-201-7/+5
|
* Cleanup Name usage.Bruce Momjian1998-07-202-16/+4
|
* Remove un-needed psort close.Bruce Momjian1998-07-191-20/+1
|
* 1) Queries using the having clause on base tables should work wellBruce Momjian1998-07-192-14/+17
| | | | | | | | | | | | | | | | | | | | | | | | | now. Here some tested features, (examples included in the patch): 1.1) Subselects in the having clause 1.2) Double nested subselects 1.3) Subselects used in the where clause and in the having clause simultaneously 1.4) Union Selects using having 1.5) Indexes on the base relations are used correctly 1.6) Unallowed Queries are prevented (e.g. qualifications in the having clause that belong to the where clause) 1.7) Insert into as select 2) Queries using the having clause on view relations also work but there are some restrictions: 2.1) Create View as Select ... Having ...; using base tables in the select 2.1.1) The Query rewrite system: 2.1.2) Why are only simple queries allowed against a view from 2.1) ? 2.2) Select ... from testview1, testview2, ... having...; 3) Bug in ExecMergeJoin ?? Regards Stefan
* Conditionally execute Junk filter only when ORDER BY of columnsBruce Momjian1998-07-191-10/+30
| | | | not in target list.
* Fix for Group ReScan suggested by Vadim.Bruce Momjian1998-07-161-1/+5
|
* Patch for ReScan of Group.Bruce Momjian1998-07-162-2/+17
|
* Allow UNION/UNION ALL in subselects.Bruce Momjian1998-07-152-3/+30
|
* Fix explain for union and inheritance. Rename Append structureBruce Momjian1998-07-152-80/+76
| | | | members to be clearer. Fix cost computation for these.
* Remove un-needed braces around single statements.Bruce Momjian1998-06-1517-114/+16
|
* Fix macros that were not properly surrounded by parens or braces.Bruce Momjian1998-06-151-6/+6
|
* Remove fork()/exec() and only do fork(). Small cleanups.Bruce Momjian1998-05-291-15/+15
|
* Fix for drop database and junk filters.Bruce Momjian1998-05-261-2/+3
|
* From: David Hartwig <daveh@insightdist.com>Marc G. Fournier1998-05-211-4/+6
| | | | | Here is a patch to remove the requirement that ORDER/GROUP BY clause identifiers be included in the target list.
* Allow cancel from client of backend query. Change some int variablesBruce Momjian1998-05-191-1/+7
| | | | to bool's.
* This patch...Bruce Momjian1998-04-272-30/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Removes the unnecessary "#define AbcRegProcedure 123"'s from pg_proc.h. 2. Changes those #defines to use the names already defined in fmgr.h. 3. Forces the make of fmgr.h in backend/Makefile instead of having it made as a dependency in access/common/Makefile *hack*hack*hack* 4. Rearranged the #includes to a less helter-skelter arrangement, also changing <file.h> to "file.h" to signify a non-system header. 5. Removed "pg_proc.h" from files where its only purpose was for the #defines removed in item #1. 6. Added "fmgr.h" to each file changed for completeness sake. Turns out that #6 was not necessary for some files because fmgr.h was being included in a roundabout way SIX levels deep by the first include. "access/genam.h" ->"access/relscan.h" ->"utils/rel.h" ->"access/strat.h" ->"access/skey.h" ->"fmgr.h" So adding fmgr.h really didn't add anything to the compile, hopefully just made it clearer to the programmer. S Darren.
* Re-apply Darren's char2-16 removal code.Bruce Momjian1998-04-261-3/+3
|
* Inline some small functions called for every row.Bruce Momjian1998-04-242-53/+5
|
* Cleanup up code.Bruce Momjian1998-04-131-2/+0
|
* Back out char2-char16 removal. Add later.Bruce Momjian1998-04-071-3/+3
|
* Hi,Bruce Momjian1998-04-061-5/+3
| | | | | | | | | | | | | | | | | | | | | | Attached you'll find a (big) patch that fixes make dep and make depend in all Makefiles where I found it to be appropriate. It also removes the dependency in Makefile.global for NAMEDATALEN and OIDNAMELEN by making backend/catalog/genbki.sh and bin/initdb/initdb.sh a little smarter. This no longer requires initdb.sh that is turned into initdb with a sed script when installing Postgres, hence initdb.sh should be renamed to initdb (after the patch has been applied :-) ) This patch is against the 6.3 sources, as it took a while to complete. Please review and apply, Cheers, Jeroen van Vianen
* The following uuencoded, gzip'd file will ...Bruce Momjian1998-03-301-3/+3
| | | | | | | | | | | 1. Remove the char2, char4, char8 and char16 types from postgresql 2. Change references of char16 to name in the regression tests. 3. Rename the char16.sql regression test to name.sql. 4. Modify the regression test scripts and outputs to match up. Might require new regression.{SYSTEM} files... Darren King
* There's a patch attached to fix gcc 2.8.x warnings, except for theBruce Momjian1998-03-302-57/+39
| | | | | | | | | | | | | | | | | | | | | | | | yyerror ones from bison. It also includes a few 'enhancements' to the C programming style (which are, of course, personal). The other patch removes the compilation of backend/lib/qsort.c, as qsort() is a standard function in stdlib.h and can be used any where else (and it is). It was only used in backend/optimizer/geqo/geqo_pool.c, backend/optimizer/path/predmig.c, and backend/storage/page/bufpage.c > > Some or all of these changes might not be appropriate for v6.3, since we > > are in beta testing and since they do not affect the current functionality. > > For those cases, how about submitting patches based on the final v6.3 > > release? There's more to come. Please review these patches. I ran the regression tests and they only failed where this was expected (random, geo, etc). Cheers, Jeroen
* I started adding the Having Clause and it works quite fine forBruce Momjian1998-03-302-3/+23
| | | | | | | | | | | | | | | | | | | | | | | | sequential scans! (I think it will also work with hash, index, etc but I did not check it out! I made some High level changes which should work for all access methods, but maybe I'm wrong. Please let me know.) Now it is possible to make queries like: select s.sname, max(p.pid), min(p.pid) from part p, supplier s where s.sid=p.sid group by s.sname having max(pid)=6 and min(pid)=1 or avg(pid)=4; Having does not work yet for queries that contain a subselect statement in the Having clause, I'll try to fix this in the next days. If there are some bugs, please let me know, I'll start to read the mailinglists now! Now here is the patch against the original 6.3 version (no snapshot!!): Stefan
* ExecReScan for MergeJoin.Vadim B. Mikheev1998-02-272-88/+75
| | | | | Marked inner tuple now is copied into mergestate->mj_MarkedTupleSlot - no more tricks arround ttc_shouldfree.
* Check SELECT permissions in subqueries.Vadim B. Mikheev1998-02-272-12/+15
|
* execScan.c: in the end of scan projInfo->pi_slot must beVadim B. Mikheev1998-02-262-28/+41
| | | | | | | | return, not a slot returned from access method (they have different TupleDesc and MergeJoin node was broken). nodeIndexscan.c: index_markpos()/index_restrpos() call index-specific mark/restr funcs and are in use now (instead of IndexScanMarkPosition()/ExecIndexRestrPos()).
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-2621-486/+516
|
* ExecReScan for Unique & Sort nodes.Vadim B. Mikheev1998-02-233-5/+53
|
* First step done,Marc G. Fournier1998-02-211-1/+12
| | | | | | | | | | | | | | | | | | | below is the patch to have views to override the permission checks for the accessed tables. Now we can do the following: CREATE VIEW db_user AS SELECT usename, usesysid, usecreatedb, usetrace, usecatupd, '**********'::text as passwd, valuntil FROM pg_user; REVOKE ALL ON pg_user FROM public; REVOKE ALL ON db_user FROM public; GRANT SELECT ON db_user TO public;
* Fix for InitPlan-s: have to copy subselect' result tuple.Vadim B. Mikheev1998-02-191-0/+12
|
* New nodeGroup.c code uses own copy of first tuple in a group.Vadim B. Mikheev1998-02-182-88/+66
| | | | Free memory after comparison in nodeUnique.c
* Fix from Vadim for simple-minded case SELECT 1 WHERE 1 IN (SELECT 1)Thomas G. Lockhart1998-02-181-2/+3
| | | | used in regression tests. No longer core dumps.
* Support for subselects.Vadim B. Mikheev1998-02-1315-153/+677
| | | | | | | ExecReScan for nodeAgg, nodeHash, nodeHashjoin, nodeNestloop and nodeResult. Fixed ExecReScan for nodeMaterial. Get rid of #ifdef INDEXSCAN_PATCH. Get rid of ExecMarkPos and ExecRestrPos in nodeNestloop.
View Lorry Controller Status