212 Commits (8c49a484e8ebb0199fba4bd68eaaedaf49b48ed0)

Author	SHA1	Message	Date
Peter Eisentraut	feb4f44d29	Message editing: remove gratuitous variations in message wording, standardize ... terms, add some clarifications, fix some untranslatable attempts at dynamic message building.	23 years ago
Bruce Momjian	46785776c4	Another pgindent run with updated typedefs.	23 years ago
Bruce Momjian	f3c3deb7d0	Update copyrights to 2003.	23 years ago
Bruce Momjian	089003fb46	pgindent run.	23 years ago
Tom Lane	45708f5ebc	Error message editing in backend/optimizer, backend/rewrite.	23 years ago
Tom Lane	aa83bc04e0	Restructure parsetree representation of DECLARE CURSOR: now it's a ... utility statement (DeclareCursorStmt) with a SELECT query dangling from it, rather than a SELECT query with a few unusual fields in it. Add code to determine whether a planned query can safely be run backwards. If DECLARE CURSOR specifies SCROLL, ensure that the plan can be run backwards by adding a Materialize plan node if it can't. Without SCROLL, you get an error if you try to fetch backwards from a cursor that can't handle it. (There is still some discussion about what the exact behavior should be, but this is necessary infrastructure in any case.) Along the way, make EXPLAIN DECLARE CURSOR work.	23 years ago
Tom Lane	8a4fdce9f2	Fix thinko in new logic about pushing down non-nullability constraints: ... constraints appearing in outer-join qualification clauses are restricted as to when and where they can be pushed down. Add regression test to catch future errors in this area.	23 years ago
Tom Lane	b5956a2f22	Detect case where an outer join can be reduced to a plain inner join ... because there are WHERE clauses that will reject the null-extended rows. Per suggestion from Brandon Craig Rhodes, 19-Nov-02.	23 years ago
Tom Lane	3646ab58b4	Remove bogus comment (too freely copied & pasted).	23 years ago
Tom Lane	c15a4c2aef	Replace planner's representation of relation sets, per pghackers discussion. ... Instead of Lists of integers, we now store variable-length bitmap sets. This should be faster as well as less error-prone.	23 years ago
Tom Lane	9f5f212475	Allow the planner to collapse explicit inner JOINs together, rather than ... necessarily following the JOIN syntax to develop the query plan. The old behavior is still available by setting GUC variable JOIN_COLLAPSE_LIMIT to 1. Also create a GUC variable FROM_COLLAPSE_LIMIT to control the similar decision about when to collapse sub-SELECT lists into their parent lists. (This behavior existed already, but the limit was always GEQO_THRESHOLD/2; now it's separately adjustable.)	23 years ago
Tom Lane	bdfbfde1b1	IN clauses appearing at top level of WHERE can now be handled as joins. ... There are two implementation techniques: the executor understands a new JOIN_IN jointype, which emits at most one matching row per left-hand row, or the result of the IN's sub-select can be fed through a DISTINCT filter and then joined as an ordinary relation. Along the way, some minor code cleanup in the optimizer; notably, break out most of the jointree-rearrangement preprocessing in planner.c and put it in a new file prep/prepjointree.c.	23 years ago