- 28 7月, 2000 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 27 7月, 2000 6 次提交
-
-
由 Tom Lane 提交于
of planning. This should reduce memory requirements for large joins.
-
由 Tom Lane 提交于
discussion on pghackers a few days ago.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
to use with a multiple-key index. Formerly we would only extract clauses that had to do with the first key of the index, which was correct but didn't exploit the index fully.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 26 7月, 2000 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
if given a node type it doesn't support. As is, wrong results from a mergejoin would go undetected.
-
由 Tom Lane 提交于
nor any OID in the reserved range (1-16383).
-
由 Tom Lane 提交于
failure to MAXALIGN the start of shmem allocable space. No reports of trouble here, just compulsive tidiness.
-
- 25 7月, 2000 3 次提交
- 24 7月, 2000 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Philip Warner 提交于
-
由 Philip Warner 提交于
- connect as appropriate user in pg_restore with db connection - dump owner of rule in pg_dump
-
由 Tom Lane 提交于
mergejoinable qual clauses, and add them to the query quals. For example, WHERE a = b AND b = c will cause us to add AND a = c. This is necessary to ensure that it's safe to use these variables as interchangeable sort keys, which is something 7.0 knows how to do. Should provide a useful improvement in planning ability, too.
-
- 23 7月, 2000 3 次提交
-
-
由 Peter Eisentraut 提交于
Don't do config.status substitutions into the regression test makefile.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
varlena elements work now. Allow assignment to previously-nonexistent subscript position to extend array, but only for 1-D arrays and only if adjacent to existing positions (could do more if we had a way to represent nulls in arrays, but I don't want to tackle that now). Arrange for assignment of NULL to an array element in UPDATE to be a no-op, rather than setting the entire array to NULL as it used to. (Throwing an error would be a reasonable alternative, but it's never done that...) Update regress test accordingly.
-
- 22 7月, 2000 11 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Jan Wieck 提交于
by Tom. Jan
-
由 Tom Lane 提交于
work as expected. THe underlying implementation is essentially 'SET foo = array_set(foo, 1, bar)', so we have to turn the items into nested invocations of array_set() to make it work correctly. Side effect: we now complain about 'UPDATE tab SET foo = bar, foo = baz' which is illegal per SQL92 but we didn't detect it before.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
a very long time.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Remove a bunch of crufty code for large-object-based arrays, which is superseded by TOAST and likely hasn't worked in a long time anyway. Clean up array code a little, and in particular eliminate its habit of scribbling on the input array (ie, modifying the input tuple :-().
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-