- 16 11月, 2007 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
- 15 11月, 2007 4 次提交
-
-
由 Tom Lane 提交于
an index, per Simon.
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
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
-
- 14 11月, 2007 22 次提交
-
-
由 Bruce Momjian 提交于
GSSAPI is industry-standard.
-
由 Magnus Hagander 提交于
per discussions (a long time ago). Documentation only, we keep full support in the code.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
wrong.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
the division of material between here and the tsearch2 contrib page, but at least it's not obviously unfinished any more.
-
由 Tom Lane 提交于
Change title to Additional Supplied Modules. Improve discussion of how to build and install 'em.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
and put it into contrib/tsearch2 compatibility module.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
compatibility package. This supports importing dumps from past versions using tsearch2, and provides the old names and API for most functions that were changed. (rewrite(ARRAY[...]) is a glaring omission, though.) Pavel Stehule and Tom Lane
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
terms defined).
-
由 Bruce Momjian 提交于
-
- 13 11月, 2007 10 次提交
-
-
由 Tom Lane 提交于
about best practice for including the module creation scripts: to wit that you should suppress NOTICE messages. This avoids creating regression failures by adding or removing comment lines in the module scripts.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Remove setting of search_path in install/uninstall scripts, since unlike other contrib modules this one does not want to let you change the installation schema.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
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).
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 12 11月, 2007 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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.
-