- 04 12月, 2007 3 次提交
-
-
由 Tom Lane 提交于
indexable-clauses list for a btree index. Formerly it just Asserted that all such clauses were opclauses, but that's no longer true in 8.3. Per bug #3796 from Matthias Schoeneich.
-
由 Tom Lane 提交于
since we supported standard FOREIGN KEY constraint syntax. It was harmless enough just sitting there, but the prospect of having to document it is surely more work than it's worth.
-
由 Magnus Hagander 提交于
to the settings used for other platforms.
-
- 03 12月, 2007 12 次提交
-
-
由 Magnus Hagander 提交于
Hannes Eder
-
由 Magnus Hagander 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
The spi documentation is pretty rudimentary, but it's a start.
-
由 Tom Lane 提交于
the former README files. Albert Cervera i Areny
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
namely that \r, \n, \t, \b, \f, \v are dumped as those two-character representations rather than a backslash and the literal control character. I had made it do the other to save some code, but this was ill-advised, because dump files in which these characters appear literally are prone to newline mangling. Fortunately, doing it the old way should only cost a few more lines of code, and not slow down the copy loop materially. Per bug #3795 from Lou Duchez.
-
由 Tom Lane 提交于
to ensure that the resulting webpages have predictable URLs, instead of ever-changing numeric IDs. The new contrib docs were the biggest offender, but some old stuff had the problem too. Also, rename a couple of new contrib sgml files for consistency's sake.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Albert Cervera i Areny
-
由 Tom Lane 提交于
trigger instead of a rule to redirect insertions, use NEW.* notation where appropriate, some other updates and adjustments. David Fetter and Tom Lane
-
- 02 12月, 2007 4 次提交
-
-
由 Tom Lane 提交于
which previously only talked about btree opclasses.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
constraint status of copied indexes (bug #3774), as well as various other small bugs such as failure to pstrdup when needed. Allow INCLUDING INDEXES indexes to be merged with identical declared indexes (perhaps not real useful, but the code is there and having it not apply to LIKE indexes seems pretty unorthogonal). Avoid useless work in generateClonedIndexStmt(). Undo some poorly chosen API changes, and put a couple of routines in modules that seem to be better places for them.
-
由 Tom Lane 提交于
lookup of the well-known OID of textout().
-
- 01 12月, 2007 5 次提交
-
-
由 Andrew Dunstan 提交于
-
由 Andrew Dunstan 提交于
implicit loading of modules, thereby breaking Safe rules. We compile and call a tiny perl function on trusted interpreter init, after which the problem does not occur.
-
由 Tom Lane 提交于
but no database changes have been made since the last CommandCounterIncrement. This should result in a significant improvement in the number of "commands" that can typically be performed within a transaction before hitting the 2^32 CommandId size limit. In particular this buys back (and more) the possible adverse consequences of my previous patch to fix plan caching behavior. The implementation requires tracking whether the current CommandCounter value has been "used" to mark any tuples. CommandCounter values stored into snapshots are presumed not to be used for this purpose. This requires some small executor changes, since the executor used to conflate the curcid of the snapshot it was using with the command ID to mark output tuples with. Separating these concepts allows some small simplifications in executor APIs. Something for the TODO list: look into having CommandCounterIncrement not do AcceptInvalidationMessages. It seems fairly bogus to be doing it there, but exactly where to do it instead isn't clear, and I'm disinclined to mess with asynchronous behavior during late beta.
-
由 Tom Lane 提交于
plan before the effects of DDL executed in an immediately prior SPI operation had been absorbed. Per report from Chris Wood. This patch has an unpleasant side effect of causing the number of CommandCounterIncrement()s done by a typical plpgsql function to approximately double. Amelioration of the consequences of that will be undertaken in a separate patch.
-
由 Magnus Hagander 提交于
-
- 30 11月, 2007 3 次提交
-
-
由 Magnus Hagander 提交于
Per complaint from Alvaro and subsequent discussion.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Jun Kuwamura
-
- 29 11月, 2007 9 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
Simon Riggs
-
由 Tom Lane 提交于
for user-facing errors, fix some poor choices of errcode, adhere to message style guide.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
reloading of operator class information on each use of LookupOpclassInfo. Had this been in place a year ago, it would have helped me find a bug in the then-new 'operator family' code. Now that we have a build farm member testing CLOBBER_CACHE_ALWAYS on a regular basis, it seems worth expending a little bit of effort here.
-
由 Bruce Momjian 提交于
Guillaume Lelarge
-
由 Tom Lane 提交于
inappropriately generic-sounding names. This is more or less free since we already forced initdb for the next beta, and it may prevent confusion or name conflicts (particularly at the C-global-symbol level) down the road. Per my proposal yesterday.
-
由 Tom Lane 提交于
by short-circuiting schema search path and ambiguous-operator resolution computations. Remarkably, this buys as much as 45% speedup of repetitive simple queries that involve operators that are not an exact match to the input datatypes. It should be marginally faster even for exact-match cases, though I've not had success in proving an improvement in benchmark tests. Per report from Guillame Smet and subsequent discussion.
-
- 28 11月, 2007 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-