- 28 1月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
> * Add the concept of dataspaces/tablespaces [tablespaces] 307d307 < * Add the concept of dataspaces/tablespaces [tablespaces]
-
由 Bruce Momjian 提交于
-
- 27 1月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 26 1月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Add group object ownership, so groups can rename/drop/grant on objects, > so we can implement roles
-
由 Tom Lane 提交于
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.)
-
- 24 1月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
users right now, not groups. Extension of has_foo_privileges functions to query the grant options. Extension of aclitem type to store grantor.
-
- 23 1月, 2003 1 次提交
-
-
由 Tom Lane 提交于
forms of ceil(), floor(), sign(). Back-patch this and other recent doc fixes in this file to the 7.3 branch.
-
- 22 1月, 2003 1 次提交
-
-
由 Tom Lane 提交于
that's selecting into a RECORD variable returns zero rows, make it assign an all-nulls row to the RECORD; this is consistent with what happens when the SELECT INTO target is not a RECORD. In support of this, tweak the SPI code so that a valid tuple descriptor is returned even when a SPI select returns no rows.
-
- 21 1月, 2003 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 19 1月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
including: - replacing all the appropriate usages of <citetitle>PostgreSQL ...</citetitle> with &cite-user;, &cite-admin;, and so on - fix an omission in the EXECUTE documentation - add some more text to the EXPLAIN documentation - improve the PL/PgSQL RETURN NEXT documentation (more work to do here) - minor markup fixes Neil Conway
-
- 18 1月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 17 1月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
set-returning functions or SRF's. for clarity.
-
- 16 1月, 2003 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
containing a volatile function), rather than only on 'Var = Var' clauses as before. This makes it practical to do flatten_join_alias_vars at the start of planning, which in turn eliminates a bunch of klugery inside the planner to deal with alias vars. As a free side effect, we now detect implied equality of non-Var expressions; for example in SELECT ... WHERE a.x = b.y and b.y = 42 we will deduce a.x = 42 and use that as a restriction qual on a. Also, we can remove the restriction introduced 12/5/02 to prevent pullup of subqueries whose targetlists contain sublinks. Still TODO: make statistical estimation routines in selfuncs.c and costsize.c smarter about expressions that are more complex than plain Vars. The need for this is considerably greater now that we have to be able to estimate the suitability of merge and hash join techniques on such expressions.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
for PL/PgSQL. Neil Conway
-
- 15 1月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
in the documentation from that same data.
-
- 14 1月, 2003 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
> o Allow PL/PgSQL to support array element assignment
-
由 Bruce Momjian 提交于
-
- 13 1月, 2003 3 次提交
-
-
由 Tom Lane 提交于
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 提交于
-
由 Bruce Momjian 提交于
-
- 12 1月, 2003 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 11 1月, 2003 4 次提交
-
-
由 Bruce Momjian 提交于
> > 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 提交于
SET_TRANSACTION.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
- 10 1月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
Currently, only RESTRICT is allowed.
-
- 09 1月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 1月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
> o Allow fastpast to pass values in portable format
-
由 Tom Lane 提交于
right thing with the destination when FETCH 0 can't return a row, don't try to stuff LONG_MAX into an int value.
-
由 Tom Lane 提交于
(ie, the one with describe-schema support). Minor code review. Adjust display of casts to use standard type names.
-