- 02 9月, 2008 2 次提交
-
-
由 Tom Lane 提交于
There are still some weak spots around JOIN USING and relation alias lists, but most errors reported within backend/parser/ now have locations.
-
由 Heikki Linnakangas 提交于
command id is the cmin, when it can in fact be a combo cid. That made rows incorrectly invisible to a transaction where a tuple was deleted by multiple aborted subtransactions. Report and patch Karl Schnaitter. Back-patch to 8.3, where combo cids was introduced.
-
- 01 9月, 2008 1 次提交
-
-
由 Peter Eisentraut 提交于
somewhat by adding CFLAGS where the compiler is used and Makefile.shlib already used CFLAGS.
-
- 30 8月, 2008 5 次提交
-
-
由 Tom Lane 提交于
Per buildfarm results.
-
由 Tom Lane 提交于
SELECT foo.*) so that it cannot be confused with a quoted identifier "*". Instead create a separate node type A_Star to represent this notation. Per pgsql-hackers discussion of 2007-Sep-27.
-
由 Tom Lane 提交于
syntax to avoid a useless store into a global variable. Per experimentation, this works better than my original thought of trying to push the code into an out-of-line subroutine.
-
由 Alvaro Herrera 提交于
David Gould
-
由 Tom Lane 提交于
clear to me why I'd not seen this message before --- on F-9 it seems to only happen if Asserts are disabled, which ought to be irrelevant. Maybe that affects a decision whether to inline get_ten(), which would be needed to expose the warning condition to the compiler? Anyway, the fix is clear.
-
- 29 8月, 2008 3 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Peter Eisentraut 提交于
change build system to use only Bison. Simplify build rules, make file names uniform. Don't build the token table header file where it is not needed.
-
由 Tom Lane 提交于
most node types used in expression trees (both before and after parse analysis). This allows us to place an error cursor in many situations where we formerly could not, because the information wasn't available beyond the very first level of parse analysis. There's a fair amount of work still to be done to persuade individual ereport() calls to actually include an error location, but this gets the initdb-forcing part of the work out of the way; and the situation is already markedly better than before for complaints about unimplementable implicit casts, such as CASE and UNION constructs with incompatible alternative data types. Per my proposal of a few days ago.
-
- 26 8月, 2008 8 次提交
-
-
由 Tom Lane 提交于
when its input is constant and the element coercion function is immutable (or nonexistent, ie, binary-coercible case). This is an oversight in the 8.3 implementation of ArrayCoerceExpr, and its result is that certain cases involving IN or NOT IN with constants don't get optimized as they should be. Per experimentation with an example from Ow Mun Heng.
-
由 Tom Lane 提交于
Fix pg_dump docs to acknowledge that you can use -Z with plain text output. Pointed out by Daniel Migowski.
-
由 Tom Lane 提交于
warnings. Peter did this for core awhile ago but evidently missed contrib.
-
由 Tom Lane 提交于
into nodes/nodeFuncs, so as to reduce wanton cross-subsystem #includes inside the backend. There's probably more that should be done along this line, but this is a start anyway.
-
由 Tom Lane 提交于
checks in ExecIndexBuildScanKeys() that were inadequate anyway: it's better to verify the correct varno on an expected index key, not just reject OUTER and INNER. This makes the entire current contents of nodeFuncs.c dead code. I'll be replacing it with some other stuff later, as per recent proposal.
-
由 Tom Lane 提交于
-
由 Magnus Hagander 提交于
the window during which backends have no statistics file to read.
-
由 Alvaro Herrera 提交于
Devrim Gunduz.
-
- 25 8月, 2008 3 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Magnus Hagander 提交于
"outage" of the statistics views. This requires making the stats collector respond to SIGHUP, like the other utility processes already did.
-
由 Magnus Hagander 提交于
it possible to call them without specifying a column list. Jaime Casanova
-
- 24 8月, 2008 1 次提交
-
-
由 Bruce Momjian 提交于
Bernd Helmle
-
- 23 8月, 2008 4 次提交
-
-
由 Teodor Sigaev 提交于
at once and ItemPointers are collected in memory. Remove tuple's killing by killtuple() if tuple was moved to another page - it could produce unaceptable overhead. Backpatch up to 8.1 because the bug was introduced by GiST's concurrency support.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Simon Riggs
-
由 Bruce Momjian 提交于
1. -i option should run vacuum analyze only on pgbench tables, not *all* tables in database. 2. pre-run cleanup step was DELETE FROM HISTORY then VACUUM HISTORY. This is just a slow version of TRUNCATE HISTORY. Simon Riggs
-
- 22 8月, 2008 4 次提交
-
-
由 Bruce Momjian 提交于
ignored because it can only be set at server start.
-
由 Tom Lane 提交于
subqueries into the same thing you'd have gotten from IN (except always with unknownEqFalse = true, so as to get the proper semantics for an EXISTS). I believe this fixes the last case within CVS HEAD in which an EXISTS could give worse performance than an equivalent IN subquery. The tricky part of this is that if the upper query probes the EXISTS for only a few rows, the hashing implementation can actually be worse than the default, and therefore we need to make a cost-based decision about which way to use. But at the time when the planner generates plans for subqueries, it doesn't really know how many times the subquery will be executed. The least invasive solution seems to be to generate both plans and postpone the choice until execution. Therefore, in a query that has been optimized this way, EXPLAIN will show two subplans for the EXISTS, of which only one will actually get executed. There is a lot more that could be done based on this infrastructure: in particular it's interesting to consider switching to the hash plan if we start out using the non-hashed plan but find a lot more upper rows going by than we expected. I have therefore left some minor inefficiencies in place, such as initializing both subplans even though we will currently only use one.
-
由 Bruce Momjian 提交于
backpatch to 8.3.X. Also fix markup that had just one bullet.
-
由 Alvaro Herrera 提交于
-
- 21 8月, 2008 5 次提交
-
-
由 Peter Eisentraut 提交于
noncomplying cases to be future-proof.
-
由 Tom Lane 提交于
to be used for SubLinks that are underneath a top-level OR clause. Just as at the very top level of WHERE, it's not necessary to be accurate about whether the sublink returns FALSE or NULL, because either result has the same impact on whether the WHERE will succeed.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 20 8月, 2008 4 次提交
-
-
由 Tom Lane 提交于
carry typmod.
-
由 Michael Meskes 提交于
-
由 Magnus Hagander 提交于
Per Microsoft knowledge base article Q201213, early versions of Windows fail when we do this. Later versions of Windows appear to have a higher limit than 64Kb, but do still fail on large sends, so we unconditionally limit it for all versions. Patch from Tom Lane.
-
由 Bruce Momjian 提交于
< o -Allow an existing index to be marked as a table's primary key > o Allow an existing index to be marked as a table's primary key
-