- 01 11月, 1999 8 次提交
-
-
由 Tom Lane 提交于
indexes to open. Avoid unnecessary work in ExecCheckPerm, too.
-
由 Tom Lane 提交于
make_const --- don't repeat cache searches that aren't needed.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Thanks to Hiroshi
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
- 31 10月, 1999 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
in the TupleDesc that the caller already has (for call from ExecMain) or can make just as easily as ExecInitJunkFilter() can (for call from ExecAppend). Also, don't bother to build a junk filter for an INSERT operation that doesn't actually need one, which is the normal case.
-
由 Tom Lane 提交于
mdnblocks. Bad enough it does an lseek, but to do it twice for no reason...
-
由 Tom Lane 提交于
that has no subplan --- saves a material amount of time for a simple INSERT ... VALUES query.
-
由 Tom Lane 提交于
In particular, don't bother to look up type information for attributes where we're not actually going to use it, and avoid copying entire tlist structure when it's not necessary.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
during initial run formation by keeping both current run and next-run tuples in the same heap (yup, Knuth is smarter than I am). And, during merge passes, make use of available sort memory to load multiple tuples from any one input 'tape' at a time, thereby improving locality of access to the temp file.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 30 10月, 1999 5 次提交
-
-
由 Tom Lane 提交于
never to commit without running regress tests...
-
由 Tom Lane 提交于
before calling execProject, when the outerPlan has returned zero tuples. I took this out under the mistaken impression that the input tuple couldn't be referenced by execProject if we weren't in GROUP BY mode. But it can, if we're in an UPDATE or DELETE...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Michael Meskes 提交于
-
- 28 10月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 27 10月, 1999 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 26 10月, 1999 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
One, it now returns the previous hook. That way people don't have to dig around in libpq-int.h for that information anymore. It previously returned void, so there should be no incompatibilities. Second, you cannot set the callback to NULL anymore. (Of course you can still call it with NULL just to get the current hook.) The way libpq uses the callback pointer, having a NULL there wasn't very healthy. Peter Eisentraut
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-