aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Stamp 8.3beta4.REL8_3_BETA4Tom Lane2007-12-03
|
* Revert COPY OUT to follow the pre-8.3 handling of ASCII control characters,Tom Lane2007-12-03
| | | | | | | | | | 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.
* Ensure that all <sect1> and <refentry> tags have IDs. This is neededTom Lane2007-12-02
| | | | | | | 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.
* Remove README files now migrated to SGML docs.Tom Lane2007-12-02
|
* Add SGML docs for contrib/dict_int and contrib/dict_xsyn.Tom Lane2007-12-02
| | | | Albert Cervera i Areny
* Improve the manual's discussion of partitioning. Recommend using aTom Lane2007-12-02
| | | | | | trigger instead of a rule to redirect insertions, use NEW.* notation where appropriate, some other updates and adjustments. David Fetter and Tom Lane
* Mention hash opclasses in 'System Dependencies on Operator Classes',Tom Lane2007-12-02
| | | | which previously only talked about btree opclasses.
* Sync release notes with CVS HEAD; various editorial improvements.Tom Lane2007-12-02
|
* Code review for LIKE ... INCLUDING INDEXES patch. Fix failure to propagateTom Lane2007-12-01
| | | | | | | | | | 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.
* Suppress compiler warnings in recent plperl patch. Avoid uselessly expensiveTom Lane2007-12-01
| | | | lookup of the well-known OID of textout().
* Revert inadvertantly committed change.Andrew Dunstan2007-12-01
|
* Workaround for perl problem where evaluating UTF8 regexes can causeAndrew Dunstan2007-12-01
| | | | | | 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.
* Avoid incrementing the CommandCounter when CommandCounterIncrement is calledTom Lane2007-11-30
| | | | | | | | | | | | | | | | | | | | 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.
* Repair bug that allowed RevalidateCachedPlan to attempt to rebuild a cachedTom Lane2007-11-30
| | | | | | | | | | 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.
* Add win32error.c to libpq, needed to resolve _dosmaperr.Magnus Hagander2007-11-30
|
* Use _dosmaperr() to deal with errors opening files in pgwin32_open().Magnus Hagander2007-11-30
| | | | Per complaint from Alvaro and subsequent discussion.
* Update release notes to current CVS.Bruce Momjian2007-11-30
|
* Update Japanese FAQ.Bruce Momjian2007-11-29
| | | | Jun Kuwamura
* Translation updatesPeter Eisentraut2007-11-29
|
* Add additional PITR documentation.Bruce Momjian2007-11-28
| | | | Simon Riggs
* Make a cleanup pass over error reports in tsearch code. Use ereportTom Lane2007-11-28
| | | | | for user-facing errors, fix some poor choices of errcode, adhere to message style guide.
* RETURN NEXT doc improvement, per Alvaro.Bruce Momjian2007-11-28
|
* Update RETURN NEXT documentation for plpgsql.Bruce Momjian2007-11-28
|
* Improve test coverage of CLOBBER_CACHE_ALWAYS by having it also forceTom Lane2007-11-28
| | | | | | | | 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.
* Plpgsql doc cleanup.Bruce Momjian2007-11-28
| | | | Guillaume Lelarge
* Adjust the names of a couple of tsearch index support functions that hadTom Lane2007-11-28
| | | | | | | 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.
* Install a lookaside cache to speed up repeated lookups of the same operatorTom Lane2007-11-28
| | | | | | | | | 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.
* Proper capitalization of IspellPeter Eisentraut2007-11-28
|
* spell checker runPeter Eisentraut2007-11-28
|
* Fix XML Schema structure for char types without length (bug #3782)Peter Eisentraut2007-11-28
|
* Improve terminologyPeter Eisentraut2007-11-28
|
* Fix typoPeter Eisentraut2007-11-28
|
* Add credit to Pavel Stehule for XML functionalityPeter Eisentraut2007-11-28
|
* Fix column numberPeter Eisentraut2007-11-28
|
* Properly recognize and announce input errors.Peter Eisentraut2007-11-28
|
* Add a few current_* variable index entries to the docs.Bruce Momjian2007-11-28
| | | | Guillaume Lelarge
* Add comments about VACUUM to free space map docs.Bruce Momjian2007-11-28
| | | | Joshua D. Drake
* Change a stop word on the right-hand-side in the thesaurus file to be anBruce Momjian2007-11-28
| | | | ERROR, not NOTICE.
* Fix plpgsql to not lookup block labels except in contexts where a block labelTom Lane2007-11-27
| | | | | | | | | | is sane (eg, EXIT argument or first part of a qualified identifier), and cause more-closely-nested record variables to take precedence over outer block labels. This cures the breakage exhibited by Marko Kreen that 8.3 no longer allowed a function's name to be used for a variable within the function, and makes plpgsql's handling of block labels more like Oracle's. It's important to fix this now because we are documenting the use of block labels as variable qualifiers for the first time in 8.3.
* Fix pg_regress to check the directory it is actually reading files from,Tom Lane2007-11-27
| | | | | | not the image that (theoretically) should exist in the current directory. Jørgen Austvik
* Add quote_literal(anyelement) to preserve (and, in fact, extend) aTom Lane2007-11-27
| | | | | | useful consequence of the former liberal implicit casting to text; namely that you can feed non-string values to quote_literal() and get unsurprising results. Per discussion.
* Suppress compiler warning.Tom Lane2007-11-27
|
* Add example of MONEY casting to numeric if locale is known.Bruce Momjian2007-11-27
|
* Make casts from xml to text independent of the XML option setting, thusPeter Eisentraut2007-11-27
| | | | | immutable and indexable. Also fix the volatility settings of some other XML-related functions.
* correct capitalizationPeter Eisentraut2007-11-27
|
* Wording improvement for MONEY casting.Bruce Momjian2007-11-27
|
* Add documentation about the issues of casting MONEY to/from numericBruce Momjian2007-11-27
| | | | types.
* Add:Bruce Momjian2007-11-26
| | | | | | | | | | | | | | | | | | | | | | | < * -Make 64-bit version of the MONEY data type < * Add locale-aware MONEY type, and support multiple currencies < < http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php < http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php < < * MONEY dumps in a locale-specific format making it difficult to < restore to a system with a different locale > > * MONEY data type > > o -Make 64-bit version of the MONEY data type > * Add locale-aware MONEY type, and support multiple currencies > > http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php > > * MONEY dumps in a locale-specific format making it difficult to > restore to a system with a different locale > * Allow MONEY to be cast to/from other numeric data types
* Change index_name to name for consistency.Peter Eisentraut2007-11-26
|
* Fix select_common_type() so that it can select a domain type, if all inputsTom Lane2007-11-26
| | | | | | | | | | | | | | | | to a UNION, CASE, or related construct are of the same domain type. The main part of this routine smashes domains to their base types, which seems necessary because the logic involves TypeCategory() and IsPreferredType(), neither of which work usefully on domains. However, we can add a first pass that just detects whether all the inputs are exactly the same type, and if so accept that without question (so long as it's not UNKNOWN). Per recent gripe from Dean Rasheed. In passing, remove some tests for InvalidOid, which have clearly been dead code for quite some time now, because getBaseType() would fail on that input. Also, clarify the manual's not-very-precise description of the existing algorithm's behavior.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 11:06:44 +0000