aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Re-run pgindent with updated list of typedefs. (Updated README shouldBruce Momjian2007-11-15
| | | | avoid this problem in the future.)
* Beef up README instructions, again.Bruce Momjian2007-11-15
|
* CUpdate README to suggest 'gmake distclean'. Add library typedefs.Bruce Momjian2007-11-15
|
* Update pgtools README to be clearer about typdefs.Bruce Momjian2007-11-15
|
* Update pgindent with current typedefs.Bruce Momjian2007-11-15
|
* When logging the recovery.conf parameters, show them quoted as they wouldPeter Eisentraut2007-11-15
| | | | appear in the configuration file.
* Add blank lines to pgindent.Bruce Momjian2007-11-15
|
* Use ftruncate() not truncate() in mdunlink. Seems Windows doesn'tTom Lane2007-11-15
| | | | support the latter.
* Update timezone data files to release 2007i of the zic database.Tom Lane2007-11-15
|
* pgindent run for 8.3.Bruce Momjian2007-11-15
|
* Translation updatesPeter Eisentraut2007-11-15
|
* Prevent re-use of a deleted relation's relfilenode until after the nextTom Lane2007-11-15
| | | | | | | | | | checkpoint. This guards against an unlikely data-loss scenario in which we re-use the relfilenode, then crash, then replay the deletion and recreation of the file. Even then we'd be OK if all insertions into the new relation had been WAL-logged ... but that's not guaranteed given all the no-WAL-logging optimizations that have recently been added. Patch by Heikki Linnakangas, per a discussion last month.
* Message improvementsPeter Eisentraut2007-11-15
|
* Add to synopsis that timeout option also applies to stop modePeter Eisentraut2007-11-15
|
* Make help synopsis consistentPeter Eisentraut2007-11-15
|
* Make synopses of -t option consistentPeter Eisentraut2007-11-15
|
* Add a rank/(rank+1) normalization option to ts_rank(). While the usefulnessTom Lane2007-11-14
| | | | | | of this seems a bit marginal, if it's useful enough to be shown in the manual then we probably ought to support doing it without double evaluation of the ts_rank function. Per my proposal earlier today.
* Fix incorrect calculation of elapsed_xlogs. Itagaki TakahiroTom Lane2007-11-14
|
* Add an Accept parameter to "simple" dictionaries. The default of trueTom Lane2007-11-14
| | | | | | | gives the old behavior; selecting false allows the dictionary to be used as a filter ahead of other dictionaries, because it will pass on rather than accept words that aren't in its stopword list. Jan Urbanski
* Clean up some stray references to tsearch2.Tom Lane2007-11-13
|
* contrib/tsearch2 need not be special-cased any longer.Tom Lane2007-11-13
|
* Resurrect the code for the rewrite(ARRAY[...]) aggregate function,Tom Lane2007-11-13
| | | | and put it into contrib/tsearch2 compatibility module.
* I find that an out-of-the-box installation of OSSP uuid 1.6.0 installsTom Lane2007-11-13
| | | | | | itself as libuuid, not libossp-uuid which was the only case expected by our build support. Install a configure test to determine which name to use (and to check that the library is present at all).
* Ensure that typmod decoration on a datatype name is validated in all cases,Tom Lane2007-11-11
| | | | | | | | | | | | | | even in code paths where we don't pay any subsequent attention to the typmod value. This seems needed in view of the fact that 8.3's generalized typmod support will accept a lot of bogus syntax, such as "timestamp(foo)" or "record(int, 42)" --- if we allow such things to pass without comment, users will get confused. Per a recent example from Greg Stark. To implement this in a way that's not very vulnerable to future bugs-of-omission, refactor the API of parse_type.c's TypeName lookup routines so that typmod validation is folded into the base lookup operation. Callers can still choose not to receive the encoded typmod, but we'll check the decoration anyway if it's present.
* Add pg_ctl -t/timeout parameter to control amount of time to wait forBruce Momjian2007-11-10
| | | | start/shutdown.
* Add missing closing / in xsd:restriction, and remove some unnecessaryTom Lane2007-11-10
| | | | | spaces for consistency. Per bug #3734 from Ben Leslie; fix by Euler Taveira de Oliveira.
* xmlGetUTF8Char()'s second argument is both input and output. FixTom Lane2007-11-10
| | | | | | uninitialized value, and avoid invoking the function nine separate times in the pg_xmlIsNameChar macro. Should resolve buildfarm failures. Per report from Ben Leslie.
* Have text search thesaurus files use "?" for stop words.Bruce Momjian2007-11-10
| | | | | | | | | Throw an error for actual stop words, rather than a warning. This fixes problems with cache reloading causing warning messages. Re-enable stop words in regression tests; was disabled by Tom. Document "?" as API change.
* Reduce error level of ROLLBACK outside a transaction from WARNING toBruce Momjian2007-11-10
| | | | NOTICE.
* Recognize RETURN QUERY via a textual test, so that QUERY doesn't need to beTom Lane2007-11-09
| | | | | | a plpgsql keyword. This avoids springing a new reserved word on plpgsql programmers. For consistency, handle RETURN NEXT the same way.
* Add an expected-results file to get regression to pass cleanly in sv_SETom Lane2007-11-09
| | | | locale, which sorts a bit differently. Per recent gripe from Magnus.
* Clean up ts_locale.h/.c. Fix broken and not-consistent-across-platformsTom Lane2007-11-09
| | | | | | behavior of wchar2char/char2wchar; this should resolve bug #3730. Avoid excess computations of pg_mblen in t_isalpha and friends. Const-ify APIs where possible.
* Second pass at improving LIKE/regex estimation in non-C locales. It turnsTom Lane2007-11-09
| | | | | | | | | | out that it's actually quite likely that a string that is an extension of the given prefix will sort as larger than the "greater" string our previous code created. To provide some defense against that, do the comparisons against a modified string instead of just the bare prefix. We tack on "Z", "z", "y", or "9", whichever is seen as largest in the current locale. Testing suggests that this is sufficient at least for cases involving ASCII data.
* Add parameter krb_realm used by GSSAPI, SSPI and KerberosMagnus Hagander2007-11-09
| | | | | | | to validate the realm of the connecting user. By default it's empty meaning no verification, which is the way Kerberos authentication has traditionally worked in PostgreSQL.
* Allow XML processing instructions starting with "xml" while prohibitingPeter Eisentraut2007-11-09
| | | | those being exactly "xml". Bug #3735 from Ben Leslie
* In tsearch code, remove !(A && B) via restructuring, for clarityBruce Momjian2007-11-09
|
* If an index depends on no columns of its table, give it a dependency on theTom Lane2007-11-08
| | | | | | | | | whole table instead, to ensure that it goes away when the table is dropped. Per bug #3723 from Sam Mason. Backpatch as far as 7.4; AFAICT 7.3 does not have the issue, because it doesn't have general-purpose expression indexes and so there must be at least one column referenced by an index.
* Fix EquivalenceClass code to handle volatile sort expressions in a moreTom Lane2007-11-08
| | | | | | | | | | | | | | predictable manner; in particular that if you say ORDER BY output-column-ref, it will in fact sort by that specific column even if there are multiple syntactic matches. An example is SELECT random() AS a, random() AS b FROM ... ORDER BY b, a; While the use-case for this might be a bit debatable, it worked as expected in earlier releases, so we should preserve the behavior for 8.3. Per my recent proposal. While at it, fix convert_subquery_pathkeys() to handle RelabelType stripping in both directions; it needs this for the same reasons make_sort_from_pathkeys does.
* Last week's patch for make_sort_from_pathkeys wasn't good enough: it hasTom Lane2007-11-08
| | | | | | | to be able to discard top-level RelabelType nodes on *both* sides of the equivalence-class-to-target-list comparison, since make_pathkey_from_sortinfo might either add or remove a RelabelType. Also fix the latter to do the removal case cleanly. Per example from Peter.
* After conferencing again with Bruce, put in more accurate XML error message.Peter Eisentraut2007-11-08
|
* Adjust test results for message changes. Darn.Peter Eisentraut2007-11-08
|
* Wording changesPeter Eisentraut2007-11-08
|
* Add sentence-ending periods.Peter Eisentraut2007-11-08
|
* Improve error messagePeter Eisentraut2007-11-08
|
* Add missing newlines to error messages, and normalize wording a bit.Peter Eisentraut2007-11-08
|
* Improve the performance of LIKE/regex estimation in non-C locales, by makingTom Lane2007-11-07
| | | | | | | | | | | | | | | | make_greater_string() try harder to generate a string that's actually greater than its input string. Before we just assumed that making a string that was memcmp-greater was enough, but it is easy to generate examples where this is not so when the locale is not C. Instead, loop until the relevant comparison function agrees that the generated string is greater than the input. Unfortunately this is probably not enough to guarantee that the generated string is greater than all extensions of the input, so we cannot relax the restriction to C locale for the LIKE/regex index optimization. But it should at least improve the odds of getting a useful selectivity estimate in prefix_selectivity(). Per example from Guillaume Smet. Backpatch to 8.1, mainly because that's what the complainant is using...
* Fix patternsel() and callers to do the right thing for NOT LIKE and the otherTom Lane2007-11-07
| | | | | | | | | | | | | | negated-match operators. patternsel had been using the supplied operator as though it were a positive-match operator, and thus obtaining a wrong result, which was even more wrong after the caller subtracted it from 1. Seems cleanest to give patternsel an explicit "negate" argument so that it knows what's going on. Also install the same factorization scheme for pattern join selectivity estimators; even though they are just stubs at the moment, this may keep someone from making the same type of mistake when they get filled out. Per report from Greg Mullane. Backpatch to 8.2 --- previous releases do not show the problem because patternsel() doesn't actually use the operator directly.
* Consistent capitalizationPeter Eisentraut2007-11-07
|
* Improve wordingPeter Eisentraut2007-11-07
|
* Error message cleanupPeter Eisentraut2007-11-07
|