- 13 Jan, 2003 3 commits
-
-
Bruce Momjian authored
-
Tom Lane authored
HAVING quals. Normally this is an insignificant effect --- but it will not be insignificant when these clauses contain sub-selects. The added costs cannot affect the planning of the query containing them, but they might have an impact when the query is a sub-query of a larger one.
-
Tom Lane authored
SubPlan nodes, else explaining queries containing sublinks may fail.
-
- 12 Jan, 2003 10 commits
-
-
Tom Lane authored
costs for expression evaluation, not only per-tuple cost as before. This extension is needed in order to deal realistically with hashed or materialized sub-selects.
-
Tom Lane authored
ExecAssignResultTypeFromTL().
-
Tom Lane authored
-
Bruce Momjian authored
-
Peter Eisentraut authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Tom Lane authored
more to be done yet, but this is a good start.
-
Bruce Momjian authored
-
- 11 Jan, 2003 10 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
supported.
-
Tom Lane authored
direction on HP-UX; our former approach has been obsolete since HPUX 9. Giles Lean
-
Bruce Momjian authored
-
Tatsuo Ishii authored
-
Bruce Momjian authored
> > I'd suggest that the runtime.sgml description explicitly say "values of > at least a few thousand are recommended for production installations". Neil Conway
-
Bruce Momjian authored
Manfred Koizar
-
Bruce Momjian authored
RELEASE_CHANGES. Manfred Koizar
-
Bruce Momjian authored
SET_TRANSACTION.
-
Peter Eisentraut authored
-
- 10 Jan, 2003 7 commits
-
-
Tom Lane authored
shared by nodeGroup, nodeAgg, and soon nodeSubplan.
-
Tom Lane authored
-
Peter Eisentraut authored
-
Peter Eisentraut authored
command with arguments.
-
Tom Lane authored
Simplify SubLink by storing just a List of operator OIDs, instead of a list of incomplete OpExprs --- that was a bizarre and bulky choice, with no redeeming social value since we have to build new OpExprs anyway when forming the plan tree.
-
Peter Eisentraut authored
Currently, only RESTRICT is allowed.
-
Peter Eisentraut authored
-
- 09 Jan, 2003 10 commits
-
-
Tom Lane authored
'NOT (x IN (subselect))', that is 'NOT (x = ANY (subselect))', rather than 'x <> ALL (subselect)' as we formerly did. This opens the door to optimizing NOT IN the same way as IN, whereas there's no hope of optimizing the expression using <>. Also, convert 'x <> ALL (subselect)' to the NOT(IN) style, so that the optimization will be available when processing rules dumped by older Postgres versions. initdb forced due to small change in SubLink node representation.
-
Tom Lane authored
-
Tom Lane authored
by having to include miscadmin.h into other header files.
-
Peter Eisentraut authored
interfaces.
-
Tom Lane authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Tom Lane authored
per gripe from Csaba Nagy. There is still potential for platform-specific behavior for values that are exactly halfway between integers, but at least we now get the expected answer for all other cases.
-
Bruce Momjian authored
-
Tom Lane authored
causes interval rounding not to work as expected in 7.3, for example SELECT '18:17:15.6'::interval(0) does not round the value. I did not force initdb, but one is needed to install the added row.
-