1996-07-09 06:22:35 +00:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
1999-02-13 23:22:53 +00:00
|
|
|
* planner.c
|
1997-09-07 05:04:48 +00:00
|
|
|
* The query optimizer external interface.
|
1996-07-09 06:22:35 +00:00
|
|
|
*
|
|
|
|
* Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
|
|
|
*
|
|
|
|
* IDENTIFICATION
|
1999-03-19 18:56:43 +00:00
|
|
|
* $Header: /cvsroot/pgsql/src/backend/optimizer/plan/planner.c,v 1.46 1999/03/19 18:56:37 momjian Exp $
|
1996-07-09 06:22:35 +00:00
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
1996-10-31 10:59:42 +00:00
|
|
|
#include <sys/types.h>
|
1998-02-13 03:37:04 +00:00
|
|
|
#include <string.h>
|
1996-10-31 10:59:42 +00:00
|
|
|
|
1996-07-09 06:22:35 +00:00
|
|
|
#include "postgres.h"
|
|
|
|
|
|
|
|
#include "nodes/pg_list.h"
|
|
|
|
#include "nodes/plannodes.h"
|
|
|
|
#include "nodes/parsenodes.h"
|
|
|
|
#include "nodes/relation.h"
|
1999-01-25 12:01:19 +00:00
|
|
|
#include "nodes/makefuncs.h"
|
|
|
|
#include "catalog/pg_type.h"
|
1997-11-25 22:07:18 +00:00
|
|
|
#include "parser/parse_expr.h"
|
1996-07-09 06:22:35 +00:00
|
|
|
|
|
|
|
#include "utils/elog.h"
|
|
|
|
#include "utils/lsyscache.h"
|
|
|
|
#include "access/heapam.h"
|
|
|
|
|
|
|
|
#include "optimizer/internal.h"
|
|
|
|
#include "optimizer/planner.h"
|
1997-09-07 05:04:48 +00:00
|
|
|
#include "optimizer/plancat.h"
|
1996-07-09 06:22:35 +00:00
|
|
|
#include "optimizer/prep.h"
|
|
|
|
#include "optimizer/planmain.h"
|
1998-02-13 03:37:04 +00:00
|
|
|
#include "optimizer/subselect.h"
|
1996-07-09 06:22:35 +00:00
|
|
|
#include "optimizer/paths.h"
|
|
|
|
#include "optimizer/cost.h"
|
|
|
|
|
|
|
|
/* DATA STRUCTURE CREATION/MANIPULATION ROUTINES */
|
|
|
|
#include "nodes/relation.h"
|
1999-02-03 20:15:53 +00:00
|
|
|
#include "optimizer/restrictinfo.h"
|
1996-07-09 06:22:35 +00:00
|
|
|
#include "optimizer/joininfo.h"
|
|
|
|
#include "optimizer/keys.h"
|
|
|
|
#include "optimizer/ordering.h"
|
|
|
|
#include "optimizer/pathnode.h"
|
|
|
|
#include "optimizer/clauses.h"
|
|
|
|
#include "optimizer/tlist.h"
|
|
|
|
#include "optimizer/var.h"
|
|
|
|
|
|
|
|
#include "executor/executor.h"
|
|
|
|
|
1999-02-03 19:31:24 +00:00
|
|
|
#include "utils/builtins.h"
|
|
|
|
#include "utils/syscache.h"
|
|
|
|
#include "access/genam.h"
|
|
|
|
#include "parser/parse_oper.h"
|
|
|
|
|
|
|
|
static bool need_sortplan(List *sortcls, Plan *plan);
|
1997-09-08 21:56:23 +00:00
|
|
|
static Plan *make_sortplan(List *tlist, List *sortcls, Plan *plannode);
|
1998-09-01 04:40:42 +00:00
|
|
|
extern Plan *make_groupPlan(List **tlist, bool tuplePerGroup,
|
1997-12-20 07:59:44 +00:00
|
|
|
List *groupClause, Plan *subplan);
|
1996-07-09 06:22:35 +00:00
|
|
|
|
|
|
|
/*****************************************************************************
|
|
|
|
*
|
1997-09-07 05:04:48 +00:00
|
|
|
* Query optimizer entry point
|
|
|
|
*
|
1996-07-09 06:22:35 +00:00
|
|
|
*****************************************************************************/
|
1998-02-26 04:46:47 +00:00
|
|
|
Plan *
|
1998-02-13 03:37:04 +00:00
|
|
|
planner(Query *parse)
|
|
|
|
{
|
|
|
|
Plan *result_plan;
|
1998-02-26 04:46:47 +00:00
|
|
|
|
1998-02-13 03:37:04 +00:00
|
|
|
PlannerQueryLevel = 1;
|
|
|
|
PlannerVarParam = NULL;
|
|
|
|
PlannerParamVar = NULL;
|
|
|
|
PlannerInitPlan = NULL;
|
|
|
|
PlannerPlanId = 0;
|
1998-02-26 04:46:47 +00:00
|
|
|
|
1998-09-03 02:34:35 +00:00
|
|
|
transformKeySetQuery(parse);
|
1998-02-26 04:46:47 +00:00
|
|
|
result_plan = union_planner(parse);
|
|
|
|
|
|
|
|
Assert(PlannerQueryLevel == 1);
|
|
|
|
if (PlannerPlanId > 0)
|
1998-02-13 03:37:04 +00:00
|
|
|
{
|
|
|
|
result_plan->initPlan = PlannerInitPlan;
|
1998-02-26 04:46:47 +00:00
|
|
|
(void) SS_finalize_plan(result_plan);
|
1998-02-13 03:37:04 +00:00
|
|
|
}
|
1998-02-26 04:46:47 +00:00
|
|
|
result_plan->nParamExec = length(PlannerParamVar);
|
|
|
|
|
1998-09-01 03:29:17 +00:00
|
|
|
return result_plan;
|
1998-02-13 03:37:04 +00:00
|
|
|
}
|
1996-07-09 06:22:35 +00:00
|
|
|
|
1997-09-07 05:04:48 +00:00
|
|
|
/*
|
1999-02-13 23:22:53 +00:00
|
|
|
* union_planner
|
1997-09-07 05:04:48 +00:00
|
|
|
*
|
|
|
|
* Invokes the planner on union queries if there are any left,
|
|
|
|
* recursing if necessary to get them all, then processes normal plans.
|
|
|
|
*
|
1996-07-09 06:22:35 +00:00
|
|
|
* Returns a query plan.
|
1997-09-07 05:04:48 +00:00
|
|
|
*
|
1996-07-09 06:22:35 +00:00
|
|
|
*/
|
1998-02-26 04:46:47 +00:00
|
|
|
Plan *
|
1998-02-13 03:37:04 +00:00
|
|
|
union_planner(Query *parse)
|
1996-07-09 06:22:35 +00:00
|
|
|
{
|
1997-09-08 02:41:22 +00:00
|
|
|
List *tlist = parse->targetList;
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
|
|
|
/***S*H***/
|
|
|
|
/* copy the original tlist, we will need the original one
|
|
|
|
* for the AGG node later on */
|
|
|
|
List *new_tlist = new_unsorted_tlist(tlist);
|
|
|
|
|
1997-09-08 02:41:22 +00:00
|
|
|
List *rangetable = parse->rtable;
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
1997-09-08 02:41:22 +00:00
|
|
|
Plan *result_plan = (Plan *) NULL;
|
1998-02-26 04:46:47 +00:00
|
|
|
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
Index rt_index;
|
1997-09-07 05:04:48 +00:00
|
|
|
|
1997-12-24 06:06:58 +00:00
|
|
|
if (parse->unionClause)
|
|
|
|
{
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
result_plan = (Plan *) plan_union_queries(parse);
|
|
|
|
/* XXX do we need to do this? bjm 12/19/97 */
|
|
|
|
tlist = preprocess_targetlist(tlist,
|
|
|
|
parse->commandType,
|
|
|
|
parse->resultRelation,
|
|
|
|
parse->rtable);
|
1997-12-24 06:06:58 +00:00
|
|
|
}
|
1999-02-03 21:18:02 +00:00
|
|
|
else if ((rt_index = first_inherit_rt_entry(rangetable)) != -1)
|
1997-09-07 05:04:48 +00:00
|
|
|
{
|
1999-01-25 12:01:19 +00:00
|
|
|
if (parse->rowMark != NULL)
|
|
|
|
elog(ERROR, "SELECT FOR UPDATE is not supported for inherit queries");
|
1997-12-29 01:13:37 +00:00
|
|
|
result_plan = (Plan *) plan_inherit_queries(parse, rt_index);
|
1997-12-20 07:59:44 +00:00
|
|
|
/* XXX do we need to do this? bjm 12/19/97 */
|
|
|
|
tlist = preprocess_targetlist(tlist,
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
parse->commandType,
|
|
|
|
parse->resultRelation,
|
|
|
|
parse->rtable);
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
|
|
|
else
|
1997-12-18 19:41:44 +00:00
|
|
|
{
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
List **vpm = NULL;
|
|
|
|
|
|
|
|
/***S*H***/
|
|
|
|
/* This is only necessary if aggregates are in use in queries like:
|
|
|
|
* SELECT sid
|
|
|
|
* FROM part
|
|
|
|
* GROUP BY sid
|
|
|
|
* HAVING MIN(pid) > 1; (pid is used but never selected for!!!)
|
|
|
|
* because the function 'query_planner' creates the plan for the lefttree
|
|
|
|
* of the 'GROUP' node and returns only those attributes contained in 'tlist'.
|
|
|
|
* The original 'tlist' contains only 'sid' here and that's why we have to
|
|
|
|
* to extend it to attributes which are not selected but are used in the
|
|
|
|
* havingQual. */
|
|
|
|
|
|
|
|
/* 'check_having_qual_for_vars' takes the havingQual and the actual 'tlist'
|
|
|
|
* as arguments and recursively scans the havingQual for attributes
|
|
|
|
* (VAR nodes) that are not contained in 'tlist' yet. If so, it creates
|
|
|
|
* a new entry and attaches it to the list 'new_tlist' (consisting of the
|
|
|
|
* VAR node and the RESDOM node as usual with tlists :-) ) */
|
|
|
|
if (parse->hasAggs)
|
1999-01-25 12:01:19 +00:00
|
|
|
{
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
if (parse->havingQual != NULL)
|
1999-01-25 12:01:19 +00:00
|
|
|
{
|
|
|
|
new_tlist = check_having_qual_for_vars(parse->havingQual,new_tlist);
|
|
|
|
}
|
|
|
|
}
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
|
|
|
new_tlist = preprocess_targetlist(new_tlist,
|
|
|
|
parse->commandType,
|
|
|
|
parse->resultRelation,
|
|
|
|
parse->rtable);
|
1999-01-25 12:01:19 +00:00
|
|
|
|
|
|
|
/* FOR UPDATE ... */
|
|
|
|
if (parse->rowMark != NULL)
|
|
|
|
{
|
|
|
|
List *l;
|
|
|
|
TargetEntry *ctid;
|
|
|
|
Resdom *resdom;
|
|
|
|
Var *var;
|
|
|
|
char *resname;
|
|
|
|
|
|
|
|
foreach (l, parse->rowMark)
|
|
|
|
{
|
|
|
|
if (!(((RowMark*)lfirst(l))->info & ROW_MARK_FOR_UPDATE))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
resname = (char*) palloc(32);
|
|
|
|
sprintf(resname, "ctid%u", ((RowMark*)lfirst(l))->rti);
|
|
|
|
resdom = makeResdom(length(new_tlist) + 1,
|
|
|
|
TIDOID,
|
|
|
|
-1,
|
|
|
|
resname,
|
|
|
|
0,
|
|
|
|
0,
|
|
|
|
1);
|
|
|
|
|
|
|
|
var = makeVar(((RowMark*)lfirst(l))->rti, -1, TIDOID,
|
|
|
|
-1, 0, ((RowMark*)lfirst(l))->rti, -1);
|
|
|
|
|
|
|
|
ctid = makeTargetEntry(resdom, (Node *) var);
|
|
|
|
new_tlist = lappend(new_tlist, ctid);
|
|
|
|
}
|
|
|
|
}
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
|
|
|
/* Here starts the original (pre having) code */
|
|
|
|
tlist = preprocess_targetlist(tlist,
|
|
|
|
parse->commandType,
|
|
|
|
parse->resultRelation,
|
|
|
|
parse->rtable);
|
|
|
|
|
|
|
|
if (parse->rtable != NULL)
|
|
|
|
{
|
|
|
|
vpm = (List **) palloc(length(parse->rtable) * sizeof(List *));
|
|
|
|
memset(vpm, 0, length(parse->rtable) * sizeof(List *));
|
|
|
|
}
|
|
|
|
PlannerVarParam = lcons(vpm, PlannerVarParam);
|
|
|
|
result_plan = query_planner(parse,
|
|
|
|
parse->commandType,
|
|
|
|
new_tlist,
|
|
|
|
(List *) parse->qual);
|
|
|
|
PlannerVarParam = lnext(PlannerVarParam);
|
|
|
|
if (vpm != NULL)
|
|
|
|
pfree(vpm);
|
1997-12-18 19:41:44 +00:00
|
|
|
}
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
1997-12-20 07:59:44 +00:00
|
|
|
/*
|
|
|
|
* If we have a GROUP BY clause, insert a group node (with the
|
|
|
|
* appropriate sort node.)
|
|
|
|
*/
|
1998-01-15 19:00:16 +00:00
|
|
|
if (parse->groupClause)
|
1997-12-20 07:59:44 +00:00
|
|
|
{
|
|
|
|
bool tuplePerGroup;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* decide whether how many tuples per group the Group node needs
|
|
|
|
* to return. (Needs only one tuple per group if no aggregate is
|
|
|
|
* present. Otherwise, need every tuple from the group to do the
|
|
|
|
* aggregation.)
|
|
|
|
*/
|
1998-01-15 19:00:16 +00:00
|
|
|
tuplePerGroup = parse->hasAggs;
|
1997-12-20 07:59:44 +00:00
|
|
|
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
/***S*H***/
|
|
|
|
/* Use 'new_tlist' instead of 'tlist' */
|
1999-02-02 17:46:17 +00:00
|
|
|
result_plan = make_groupPlan(&new_tlist,
|
|
|
|
tuplePerGroup,
|
|
|
|
parse->groupClause,
|
|
|
|
result_plan);
|
1997-12-20 07:59:44 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If aggregate is present, insert the agg node
|
|
|
|
*/
|
1998-01-15 19:00:16 +00:00
|
|
|
if (parse->hasAggs)
|
1997-12-20 07:59:44 +00:00
|
|
|
{
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
int old_length=0, new_length=0;
|
|
|
|
|
1999-01-25 18:02:28 +00:00
|
|
|
/* Create the Agg node but use 'tlist' not 'new_tlist' as target list because we
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
* don't want the additional attributes (only used for the havingQual, see above)
|
|
|
|
* to show up in the result */
|
1998-02-26 04:46:47 +00:00
|
|
|
result_plan = (Plan *) make_agg(tlist, result_plan);
|
1997-12-20 07:59:44 +00:00
|
|
|
|
|
|
|
/*
|
1999-02-02 17:46:17 +00:00
|
|
|
* get the varno/attno entries to the appropriate references to
|
1998-01-15 19:00:16 +00:00
|
|
|
* the result tuple of the subplans.
|
1997-12-20 07:59:44 +00:00
|
|
|
*/
|
1999-02-03 21:18:02 +00:00
|
|
|
((Agg *) result_plan)->aggs = get_agg_tlist_references((Agg *) result_plan);
|
1998-03-30 16:36:43 +00:00
|
|
|
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
/***S*H***/
|
|
|
|
if(parse->havingQual!=NULL)
|
|
|
|
{
|
|
|
|
List *clause;
|
|
|
|
List **vpm = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
/* stuff copied from above to handle the use of attributes from outside
|
|
|
|
* in subselects */
|
1997-12-20 07:59:44 +00:00
|
|
|
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
if (parse->rtable != NULL)
|
|
|
|
{
|
|
|
|
vpm = (List **) palloc(length(parse->rtable) * sizeof(List *));
|
|
|
|
memset(vpm, 0, length(parse->rtable) * sizeof(List *));
|
|
|
|
}
|
|
|
|
PlannerVarParam = lcons(vpm, PlannerVarParam);
|
|
|
|
|
|
|
|
|
|
|
|
/* convert the havingQual to conjunctive normal form (cnf) */
|
1999-03-19 18:56:43 +00:00
|
|
|
parse->havingQual = (Node *) cnfify((Expr *)(Node *) parse->havingQual,true);
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
|
|
|
/* There is a subselect in the havingQual, so we have to process it
|
|
|
|
* using the same function as for a subselect in 'where' */
|
|
|
|
if (parse->hasSubLinks)
|
|
|
|
{
|
1999-03-19 18:56:43 +00:00
|
|
|
parse->havingQual =
|
|
|
|
(Node *) SS_process_sublinks((Node *) parse->havingQual);
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Calculate the opfids from the opnos (=select the correct functions for
|
|
|
|
* the used VAR datatypes) */
|
1999-03-19 18:56:43 +00:00
|
|
|
parse->havingQual = (Node *) fix_opids((List *) parse->havingQual);
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
|
|
|
|
((Agg *) result_plan)->plan.qual=(List *) parse->havingQual;
|
|
|
|
|
|
|
|
/* Check every clause of the havingQual for aggregates used and append
|
1999-02-02 17:46:17 +00:00
|
|
|
* them to result_plan->aggs
|
|
|
|
*/
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
foreach(clause, ((Agg *) result_plan)->plan.qual)
|
|
|
|
{
|
|
|
|
/* Make sure there are aggregates in the havingQual
|
1999-02-02 17:46:17 +00:00
|
|
|
* if so, the list must be longer after check_having_qual_for_aggs
|
|
|
|
*/
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
old_length=length(((Agg *) result_plan)->aggs);
|
|
|
|
|
|
|
|
((Agg *) result_plan)->aggs = nconc(((Agg *) result_plan)->aggs,
|
|
|
|
check_having_qual_for_aggs((Node *) lfirst(clause),
|
|
|
|
((Agg *) result_plan)->plan.lefttree->targetlist,
|
|
|
|
((List *) parse->groupClause)));
|
|
|
|
|
|
|
|
/* Have a look at the length of the returned list. If there is no
|
|
|
|
* difference, no aggregates have been found and that means, that
|
|
|
|
* the Qual belongs to the where clause */
|
|
|
|
if (((new_length=length(((Agg *) result_plan)->aggs)) == old_length) ||
|
|
|
|
(new_length == 0))
|
|
|
|
{
|
|
|
|
elog(ERROR,"This could have been done in a where clause!!");
|
|
|
|
return (Plan *)NIL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
PlannerVarParam = lnext(PlannerVarParam);
|
|
|
|
if (vpm != NULL)
|
|
|
|
pfree(vpm);
|
|
|
|
}
|
|
|
|
}
|
1999-01-25 12:01:19 +00:00
|
|
|
|
1997-09-07 05:04:48 +00:00
|
|
|
/*
|
|
|
|
* For now, before we hand back the plan, check to see if there is a
|
|
|
|
* user-specified sort that needs to be done. Eventually, this will
|
|
|
|
* be moved into the guts of the planner s.t. user specified sorts
|
|
|
|
* will be considered as part of the planning process. Since we can
|
|
|
|
* only make use of user-specified sorts in special cases, we can do
|
|
|
|
* the optimization step later.
|
|
|
|
*/
|
|
|
|
|
1997-12-27 06:41:41 +00:00
|
|
|
if (parse->uniqueFlag)
|
1997-09-07 05:04:48 +00:00
|
|
|
{
|
1997-12-27 06:41:41 +00:00
|
|
|
Plan *sortplan = make_sortplan(tlist, parse->sortClause, result_plan);
|
1997-09-07 05:04:48 +00:00
|
|
|
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
return ((Plan *) make_unique(tlist, sortplan, parse->uniqueFlag));
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
1999-02-03 19:31:24 +00:00
|
|
|
if (parse->sortClause && need_sortplan(parse->sortClause, result_plan))
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
return (make_sortplan(tlist, parse->sortClause, result_plan));
|
1997-09-07 05:04:48 +00:00
|
|
|
else
|
Hi!
INTERSECT and EXCEPT is available for postgresql-v6.4!
The patch against v6.4 is included at the end of the current text
(in uuencoded form!)
I also included the text of my Master's Thesis. (a postscript
version). I hope that you find something of it useful and would be
happy if parts of it find their way into the PostgreSQL documentation
project (If so, tell me, then I send the sources of the document!)
The contents of the document are:
-) The first chapter might be of less interest as it gives only an
overview on SQL.
-) The second chapter gives a description on much of PostgreSQL's
features (like user defined types etc. and how to use these features)
-) The third chapter starts with an overview of PostgreSQL's internal
structure with focus on the stages a query has to pass (i.e. parser,
planner/optimizer, executor). Then a detailed description of the
implementation of the Having clause and the Intersect/Except logic is
given.
Originally I worked on v6.3.2 but never found time enough to prepare
and post a patch. Now I applied the changes to v6.4 to get Intersect
and Except working with the new version. Chapter 3 of my documentation
deals with the changes against v6.3.2, so keep that in mind when
comparing the parts of the code printed there with the patched sources
of v6.4.
Here are some remarks on the patch. There are some things that have
still to be done but at the moment I don't have time to do them
myself. (I'm doing my military service at the moment) Sorry for that
:-(
-) I used a rewrite technique for the implementation of the Except/Intersect
logic which rewrites the query to a semantically equivalent query before
it is handed to the rewrite system (for views, rules etc.), planner,
executor etc.
-) In v6.3.2 the types of the attributes of two select statements
connected by the UNION keyword had to match 100%. In v6.4 the types
only need to be familiar (i.e. int and float can be mixed). Since this
feature did not exist when I worked on Intersect/Except it
does not work correctly for Except/Intersect queries WHEN USED IN
COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the
resulting table. This is because until now the types of the attributes of
the first select statement have been used for the resulting table.
When Intersects and/or Excepts are used in combination with Unions it
might happen, that the first select statement of the original query
appears at another position in the query which will be executed. The reason
for this is the technique used for the implementation of
Except/Intersect which does a query rewrite!)
NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT
queries!!!
-) I had to add the field intersect_clause to some data structures
but did not find time to implement printfuncs for the new field.
This does NOT break the debug modes but when an Except/Intersect
is used the query debug output will be the already rewritten query.
-) Massive changes to the grammar rules for SELECT and INSERT statements
have been necessary (see comments in gram.y and documentation for
deatails) in order to be able to use mixed queries like
(SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...;
-) When using UNION/EXCEPT/INTERSECT you will get:
NOTICE: equal: "Don't know if nodes of type xxx are equal".
I did not have time to add comparsion support for all the needed nodes,
but the default behaviour of the function equal met my requirements.
I did not dare to supress this message!
That's the reason why the regression test for union will fail: These
messages are also included in the union.out file!
-) Somebody of you changed the union_planner() function for v6.4
(I copied the targetlist to new_tlist and that was removed and
replaced by a cleanup of the original targetlist). These chnages
violated some having queries executed against views so I changed
it back again. I did not have time to examine the differences between the
two versions but now it works :-)
If you want to find out, try the file queries/view_having.sql on
both versions and compare the results . Two queries won't produce a
correct result with your version.
regards
Stefan
1999-01-18 00:10:17 +00:00
|
|
|
return ((Plan *) result_plan);
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
1996-07-09 06:22:35 +00:00
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
1999-02-13 23:22:53 +00:00
|
|
|
* make_sortplan
|
1997-09-07 05:04:48 +00:00
|
|
|
* Returns a sortplan which is basically a SORT node attached to the
|
|
|
|
* top of the plan returned from the planner. It also adds the
|
|
|
|
* cost of sorting into the plan.
|
|
|
|
*
|
1996-07-09 06:22:35 +00:00
|
|
|
* sortkeys: ( resdom1 resdom2 resdom3 ...)
|
|
|
|
* sortops: (sortop1 sortop2 sortop3 ...)
|
|
|
|
*/
|
1997-09-08 02:41:22 +00:00
|
|
|
static Plan *
|
1997-09-08 21:56:23 +00:00
|
|
|
make_sortplan(List *tlist, List *sortcls, Plan *plannode)
|
1996-07-09 06:22:35 +00:00
|
|
|
{
|
1997-09-08 02:41:22 +00:00
|
|
|
Plan *sortplan = (Plan *) NULL;
|
|
|
|
List *temp_tlist = NIL;
|
|
|
|
List *i = NIL;
|
|
|
|
Resdom *resnode = (Resdom *) NULL;
|
|
|
|
Resdom *resdom = (Resdom *) NULL;
|
|
|
|
int keyno = 1;
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* First make a copy of the tlist so that we don't corrupt the the
|
|
|
|
* original .
|
|
|
|
*/
|
|
|
|
|
|
|
|
temp_tlist = new_unsorted_tlist(tlist);
|
|
|
|
|
|
|
|
foreach(i, sortcls)
|
|
|
|
{
|
1997-09-08 02:41:22 +00:00
|
|
|
SortClause *sortcl = (SortClause *) lfirst(i);
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
resnode = sortcl->resdom;
|
|
|
|
resdom = tlist_resdom(temp_tlist, resnode);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Order the resdom keys and replace the operator OID for each key
|
|
|
|
* with the regproc OID.
|
|
|
|
*/
|
|
|
|
resdom->reskey = keyno;
|
|
|
|
resdom->reskeyop = get_opcode(sortcl->opoid);
|
|
|
|
keyno += 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
sortplan = (Plan *) make_sort(temp_tlist,
|
1999-02-09 17:03:14 +00:00
|
|
|
_NONAME_RELATION_ID_,
|
1997-09-07 05:04:48 +00:00
|
|
|
(Plan *) plannode,
|
|
|
|
length(sortcls));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* XXX Assuming that an internal sort has no. cost. This is wrong, but
|
|
|
|
* given that at this point, we don't know the no. of tuples returned,
|
|
|
|
* etc, we can't do better than to add a constant cost. This will be
|
|
|
|
* fixed once we move the sort further into the planner, but for now
|
|
|
|
* ... functionality....
|
1996-07-09 06:22:35 +00:00
|
|
|
*/
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
sortplan->cost = plannode->cost;
|
|
|
|
|
1998-09-01 03:29:17 +00:00
|
|
|
return sortplan;
|
1996-07-09 06:22:35 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* pg_checkretval() -- check return value of a list of sql parse
|
1997-09-07 05:04:48 +00:00
|
|
|
* trees.
|
1996-07-09 06:22:35 +00:00
|
|
|
*
|
|
|
|
* The return value of a sql function is the value returned by
|
|
|
|
* the final query in the function. We do some ad-hoc define-time
|
|
|
|
* type checking here to be sure that the user is returning the
|
|
|
|
* type he claims.
|
|
|
|
*/
|
|
|
|
void
|
1997-09-08 21:56:23 +00:00
|
|
|
pg_checkretval(Oid rettype, QueryTreeList *queryTreeList)
|
1996-07-09 06:22:35 +00:00
|
|
|
{
|
1997-09-08 02:41:22 +00:00
|
|
|
Query *parse;
|
|
|
|
List *tlist;
|
|
|
|
List *rt;
|
|
|
|
int cmd;
|
|
|
|
Type typ;
|
|
|
|
Resdom *resnode;
|
|
|
|
Relation reln;
|
|
|
|
Oid relid;
|
|
|
|
Oid tletype;
|
|
|
|
int relnatts;
|
|
|
|
int i;
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/* find the final query */
|
|
|
|
parse = queryTreeList->qtrees[queryTreeList->len - 1];
|
|
|
|
|
|
|
|
/*
|
|
|
|
* test 1: if the last query is a utility invocation, then there had
|
|
|
|
* better not be a return value declared.
|
|
|
|
*/
|
|
|
|
if (parse->commandType == CMD_UTILITY)
|
|
|
|
{
|
|
|
|
if (rettype == InvalidOid)
|
|
|
|
return;
|
|
|
|
else
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "return type mismatch in function decl: final query is a catalog utility");
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* okay, it's an ordinary query */
|
|
|
|
tlist = parse->targetList;
|
|
|
|
rt = parse->rtable;
|
|
|
|
cmd = parse->commandType;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* test 2: if the function is declared to return no value, then the
|
|
|
|
* final query had better not be a retrieve.
|
|
|
|
*/
|
1996-07-09 06:22:35 +00:00
|
|
|
if (rettype == InvalidOid)
|
1997-09-07 05:04:48 +00:00
|
|
|
{
|
|
|
|
if (cmd == CMD_SELECT)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR,
|
1997-09-07 05:04:48 +00:00
|
|
|
"function declared with no return type, but final query is a retrieve");
|
|
|
|
else
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* by here, the function is declared to return some type */
|
1997-11-25 22:07:18 +00:00
|
|
|
if ((typ = typeidType(rettype)) == NULL)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "can't find return type %d for function\n", rettype);
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* test 3: if the function is declared to return a value, then the
|
|
|
|
* final query had better be a retrieve.
|
|
|
|
*/
|
|
|
|
if (cmd != CMD_SELECT)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return type %s, but final query is not a retrieve", typeTypeName(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* test 4: for base type returns, the target list should have exactly
|
|
|
|
* one entry, and its type should agree with what the user declared.
|
|
|
|
*/
|
|
|
|
|
1997-11-25 22:07:18 +00:00
|
|
|
if (typeTypeRelid(typ) == InvalidOid)
|
1997-09-07 05:04:48 +00:00
|
|
|
{
|
1998-07-20 21:18:35 +00:00
|
|
|
if (ExecTargetListLength(tlist) > 1)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return %s returns multiple values in final retrieve", typeTypeName(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
resnode = (Resdom *) ((TargetEntry *) lfirst(tlist))->resdom;
|
|
|
|
if (resnode->restype != rettype)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "return type mismatch in function: declared to return %s, returns %s", typeTypeName(typ), typeidTypeName(resnode->restype));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/* by here, base return types match */
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the target list is of length 1, and the type of the varnode in
|
|
|
|
* the target list is the same as the declared return type, this is
|
|
|
|
* okay. This can happen, for example, where the body of the function
|
|
|
|
* is 'retrieve (x = func2())', where func2 has the same return type
|
|
|
|
* as the function that's calling it.
|
|
|
|
*/
|
1998-07-20 21:18:35 +00:00
|
|
|
if (ExecTargetListLength(tlist) == 1)
|
1997-09-07 05:04:48 +00:00
|
|
|
{
|
|
|
|
resnode = (Resdom *) ((TargetEntry *) lfirst(tlist))->resdom;
|
|
|
|
if (resnode->restype == rettype)
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* By here, the procedure returns a (set of) tuples. This part of the
|
|
|
|
* typechecking is a hack. We look up the relation that is the
|
|
|
|
* declared return type, and be sure that attributes 1 .. n in the
|
|
|
|
* target list match the declared types.
|
|
|
|
*/
|
1997-11-25 22:07:18 +00:00
|
|
|
reln = heap_open(typeTypeRelid(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
if (!RelationIsValid(reln))
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "cannot open relation relid %d", typeTypeRelid(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
relid = reln->rd_id;
|
|
|
|
relnatts = reln->rd_rel->relnatts;
|
|
|
|
|
1998-07-20 21:18:35 +00:00
|
|
|
if (ExecTargetListLength(tlist) != relnatts)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return type %s does not retrieve (%s.*)", typeTypeName(typ), typeTypeName(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
/* expect attributes 1 .. n in order */
|
|
|
|
for (i = 1; i <= relnatts; i++)
|
|
|
|
{
|
1997-09-08 02:41:22 +00:00
|
|
|
TargetEntry *tle = lfirst(tlist);
|
|
|
|
Node *thenode = tle->expr;
|
1997-09-07 05:04:48 +00:00
|
|
|
|
|
|
|
tlist = lnext(tlist);
|
|
|
|
tletype = exprType(thenode);
|
|
|
|
|
1999-02-21 03:49:55 +00:00
|
|
|
#ifdef NOT_USED /* fix me */
|
1997-09-07 05:04:48 +00:00
|
|
|
/* this is tedious */
|
|
|
|
if (IsA(thenode, Var))
|
|
|
|
tletype = (Oid) ((Var *) thenode)->vartype;
|
|
|
|
else if (IsA(thenode, Const))
|
|
|
|
tletype = (Oid) ((Const *) thenode)->consttype;
|
|
|
|
else if (IsA(thenode, Param))
|
|
|
|
tletype = (Oid) ((Param *) thenode)->paramtype;
|
|
|
|
else if (IsA(thenode, Expr))
|
|
|
|
tletype = Expr;
|
1997-09-08 21:56:23 +00:00
|
|
|
|
1997-09-07 05:04:48 +00:00
|
|
|
else if (IsA(thenode, LispList))
|
|
|
|
{
|
|
|
|
thenode = lfirst(thenode);
|
|
|
|
if (IsA(thenode, Oper))
|
|
|
|
tletype = (Oid) get_opresulttype((Oper *) thenode);
|
|
|
|
else if (IsA(thenode, Func))
|
|
|
|
tletype = (Oid) get_functype((Func *) thenode);
|
|
|
|
else
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return type %s does not retrieve (%s.all)", typeTypeName(typ), typeTypeName(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
|
|
|
else
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return type %s does not retrieve (%s.all)", typeTypeName(typ), typeTypeName(typ));
|
1997-09-05 20:20:56 +00:00
|
|
|
#endif
|
1997-09-07 05:04:48 +00:00
|
|
|
/* reach right in there, why don't you? */
|
|
|
|
if (tletype != reln->rd_att->attrs[i - 1]->atttypid)
|
1998-01-07 21:07:04 +00:00
|
|
|
elog(ERROR, "function declared to return type %s does not retrieve (%s.all)", typeTypeName(typ), typeTypeName(typ));
|
1997-09-07 05:04:48 +00:00
|
|
|
}
|
1996-07-09 06:22:35 +00:00
|
|
|
|
1997-09-07 05:04:48 +00:00
|
|
|
heap_close(reln);
|
1996-07-09 06:22:35 +00:00
|
|
|
|
1997-09-07 05:04:48 +00:00
|
|
|
/* success */
|
|
|
|
return;
|
1996-07-09 06:22:35 +00:00
|
|
|
}
|
1999-02-03 19:31:24 +00:00
|
|
|
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Support function for need_sortplan
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
static TargetEntry *
|
|
|
|
get_matching_tle(Plan *plan, Resdom *resdom)
|
|
|
|
{
|
|
|
|
List *i;
|
|
|
|
TargetEntry *tle;
|
|
|
|
|
|
|
|
foreach (i, plan->targetlist) {
|
|
|
|
tle = (TargetEntry *)lfirst(i);
|
|
|
|
if (tle->resdom->resno == resdom->resno)
|
|
|
|
return tle;
|
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Check if a user requested ORDER BY is already satisfied by
|
|
|
|
* the choosen index scan.
|
|
|
|
*
|
|
|
|
* Returns TRUE if sort is required, FALSE if can be omitted.
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
static bool
|
|
|
|
need_sortplan(List *sortcls, Plan *plan)
|
|
|
|
{
|
|
|
|
Relation indexRel;
|
|
|
|
IndexScan *indexScan;
|
|
|
|
Oid indexId;
|
|
|
|
List *i;
|
|
|
|
HeapTuple htup;
|
|
|
|
Form_pg_index index_tup;
|
|
|
|
int key_no = 0;
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Must be an IndexScan
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
if (nodeTag(plan) != T_IndexScan) {
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
indexScan = (IndexScan *)plan;
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Should not have left- or righttree
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
if (plan->lefttree != NULL) {
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
if (plan->righttree != NULL) {
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Must be a single index scan
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
if (length(indexScan->indxid) != 1) {
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Indices can only have up to 8 attributes. So an ORDER BY using
|
|
|
|
* more that 8 attributes could never be satisfied by an index.
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
if (length(sortcls) > 8) {
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* The choosen Index must be a btree
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
indexId = lfirsti(indexScan->indxid);
|
|
|
|
|
|
|
|
indexRel = index_open(indexId);
|
|
|
|
if (strcmp(nameout(&(indexRel->rd_am->amname)), "btree") != 0) {
|
|
|
|
heap_close(indexRel);
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
heap_close(indexRel);
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Fetch the index tuple
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
htup = SearchSysCacheTuple(INDEXRELID,
|
|
|
|
ObjectIdGetDatum(indexId), 0, 0, 0);
|
|
|
|
if (!HeapTupleIsValid(htup)) {
|
|
|
|
elog(ERROR, "cache lookup for index %d failed", indexId);
|
|
|
|
}
|
|
|
|
index_tup = (Form_pg_index) GETSTRUCT(htup);
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Check if all the sort clauses match the attributes in the index
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
foreach (i, sortcls) {
|
|
|
|
SortClause *sortcl;
|
|
|
|
Resdom *resdom;
|
|
|
|
TargetEntry *tle;
|
|
|
|
Var *var;
|
|
|
|
|
|
|
|
sortcl = (SortClause *) lfirst(i);
|
|
|
|
|
|
|
|
resdom = sortcl->resdom;
|
|
|
|
tle = get_matching_tle(plan, resdom);
|
|
|
|
if (tle == NULL) {
|
|
|
|
/* ----------
|
|
|
|
* Could this happen?
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
if (nodeTag(tle->expr) != T_Var) {
|
|
|
|
/* ----------
|
|
|
|
* The target list expression isn't a var, so it
|
|
|
|
* cannot be the indexed attribute
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
var = (Var *)(tle->expr);
|
|
|
|
|
|
|
|
if (var->varno != indexScan->scan.scanrelid) {
|
|
|
|
/* ----------
|
|
|
|
* This Var isn't from the scan relation. So it isn't
|
|
|
|
* that of the index
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (var->varattno != index_tup->indkey[key_no]) {
|
|
|
|
/* ----------
|
|
|
|
* It isn't the indexed attribute.
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (oprid(oper("<", resdom->restype, resdom->restype, FALSE)) != sortcl->opoid) {
|
|
|
|
/* ----------
|
|
|
|
* Sort order isn't in ascending order.
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
key_no++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------
|
|
|
|
* Index matches ORDER BY - sort not required
|
|
|
|
* ----------
|
|
|
|
*/
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|