- 04 1月, 2004 9 次提交
-
-
由 Tom Lane 提交于
run the data through cpp, and we know of at least one platform where unusual cpp behavior breaks the process. So remove the cpp step, and make consequent simplifications.
-
由 Tom Lane 提交于
be cast to unsigned char. We have learned this the hard way before.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
teaching the latter to accept either RestrictInfo nodes or bare clause expressions; and cache the selectivity result in the RestrictInfo node when possible. This extends the caching behavior of approx_selectivity to many more contexts, and should reduce duplicate selectivity calculations.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Problem report on True64 Unix by Nikola Milutinovic.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
first time generate an OR indexscan for a two-column index when the WHERE condition is like 'col1 = foo AND (col2 = bar OR col2 = baz)' --- before, the OR had to be on the first column of the index or we'd not notice the possibility of using it. Some progress towards extracting OR indexscans from subclauses of an OR that references multiple relations, too, although this code is #ifdef'd out because it needs more work.
-
- 03 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 02 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
This ensures stdout is kept in sync with messages on stderr. Per report from Olaf Ferger.
-
- 01 1月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 31 12月, 2003 5 次提交
-
-
由 Tom Lane 提交于
fields: now they are valid whenever the clause is a binary opclause, not only when it is a potential join clause (there is a new boolean field canjoin to signal the latter condition). This lets us avoid recomputing the relid sets over and over while examining indexes. Still more work to do to make this as useful as it could be, because there are places that could use the info but don't have access to the RestrictInfo node.
-
由 Tom Lane 提交于
LC_CTYPE settings of a database.
-
由 Bruce Momjian 提交于
required.
-
由 Tom Lane 提交于
just look for common clauses that can be pulled out of ORs. Per recent discussion, extracting common clauses seems to be the only really useful effect of normalization, and if we do it explicitly then we can avoid cluttering the qual with partially-redundant duplicated expressions, which was an unpleasant side-effect of the old approach.
-
由 Tom Lane 提交于
number-of-buckets that exceeds the size we actually plan to allow the hash table to grow to. Per trouble report from Sean Shanny.
-
- 30 12月, 2003 5 次提交
-
-
由 Tom Lane 提交于
call. You'd think this would cause some problems, but because of the way hash_create is coded, the only side-effect was creation of a useless memory context for the hashtable.
-
由 Tom Lane 提交于
memory contexts belonging to hash tables. Makes the memory stats printout a little more useful.
-
由 Tom Lane 提交于
conditions is overkill; set_union() does the job about as well, and much more efficiently. Furthermore this avoids assuming that canonicalize_qual() will check for duplicate clauses at all, which it may not always do.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
showed that for common operator names such as '=', the pallocs done by this routine occupied a surprisingly large fraction of the total time for the parser to process an operator.
-
- 29 12月, 2003 4 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
about whether it is applied before or after eval_const_expressions(). I believe there were some corner cases where the system would fail to recognize that a partial index is applicable because of the previous inconsistency. Store normal rather than 'implicit AND' representations of constraints and index predicates in the catalogs. initdb forced due to representation change of constraints/predicates.
-
由 Tom Lane 提交于
could never exceed 30K. Per report from Andreas Pflug.
-
由 Tom Lane 提交于
PQexecFinish(). Per report from Andreas Pflug.
-
- 28 12月, 2003 2 次提交
- 27 12月, 2003 2 次提交
-
-
由 Tom Lane 提交于
index entries.
-
由 Michael Meskes 提交于
-
- 25 12月, 2003 4 次提交
-
-
由 Bruce Momjian 提交于
fork/exec'd, in the same mode as the previous patch for backends. Claudio Natoli
-
由 Bruce Momjian 提交于
special meaning of these terms in pg_hba.conf. Also changes ugly pg_hba.conf IPv6 netmask of ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff to ::1/128. Andrew Dunstan
-
由 Bruce Momjian 提交于
> > needed, and other people in the past asked about it too. > > It is in Oracle, but you aren't exactly on the spot. It should be > > IYYY - 4 digits ('2003') > IYY - 3 digits ('003') > IY - 2 digits ('03') > I - 1 digit ('3') Here is an updated patch that does that. Kurt Roeckx
-
由 Michael Meskes 提交于
-
- 24 12月, 2003 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Patch inspired by original submission from ViSolve.
-
由 Tom Lane 提交于
prefix would fail, because the new path did not get propagated to where it needed to be. Note this would fail even with --enable-depend.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
by means of arbitrarily renaming tables the other test depends on.
-
由 Tom Lane 提交于
table name conflict against rangefuncs test.
-