- 30 7月, 2000 1 次提交
-
-
由 Tom Lane 提交于
updated to new fmgr style. Deleted hoary old functions for compatibility with pre-6.1 representations of these datatypes.
-
- 29 7月, 2000 1 次提交
-
-
由 Tom Lane 提交于
I did not force. I marked numeric as compressable-but-not-move-off-able, partly to test that storage mode and partly because I've got doubts that numerics are large enough to need external storage.
-
- 28 7月, 2000 18 次提交
-
-
由 Thomas G. Lockhart 提交于
Note that this has changed some of the edge cases for what is accepted as a type name and/or column id. Regression test passes, but more tweaks may be coming...
-
由 Tom Lane 提交于
the planner may try to generate them as a result of transitivity of the existing int2-vs-int4 and int4-vs-int8 operators. In fact, it is now necessary that mergejoinable cross-datatype operators form closed sets. Add an opr_sanity regress test to detect missing operators.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
eval_const_expressions tries to simplify an SQL function.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
for today's snapshot Andreas
-
由 Bruce Momjian 提交于
FreeBSD/Intel and DecUX/Alpha machines. The bug appears in postgresql 6.5.3 and 7.0.2. Can someone please review it and apply it to the source tree? Sometimes when the postgres connection dies it is necessary to attempt to reconnect. Calling the pgconnection::Connect method in a derived class leaks memory because it does not clear the current connection (if there is one). These patches ensures that any open connections are closed before attempting to open a new one. -Michael Richards
-
由 Bruce Momjian 提交于
-
由 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 2 次提交
-
-
由 Peter Eisentraut 提交于
Don't do config.status substitutions into the regression test makefile.
-
由 Tom Lane 提交于
-