- 14 11月, 2007 7 次提交
-
-
由 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.
-
- 11 11月, 2007 13 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
remove transactions use create or replace function make formatting consistent set search patch on first line Add documentation on modifying *.sql to set the search patch, and mention that major upgrades should still run the installation scripts. Some of these issues were spotted by Tom today.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
or will never be converted.
-
由 Bruce Momjian 提交于
start/shutdown.
-
由 Tom Lane 提交于
multiple rows. I had thought this case was covered, but there was no example in the obvious section to look in.
-
由 Tom Lane 提交于
spaces for consistency. Per bug #3734 from Ben Leslie; fix by Euler Taveira de Oliveira.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
uninitialized value, and avoid invoking the function nine separate times in the pg_xmlIsNameChar macro. Should resolve buildfarm failures. Per report from Ben Leslie.
-
- 10 11月, 2007 8 次提交
-
-
由 Bruce Momjian 提交于
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.
-
由 Bruce Momjian 提交于
NOTICE.
-
由 Bruce Momjian 提交于
-
由 Joe Conway 提交于
per suggestion from Tom Lane. This fixes crash-bug reported by Stefan Schwarzer.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
a plpgsql keyword. This avoids springing a new reserved word on plpgsql programmers. For consistency, handle RETURN NEXT the same way.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
locale, which sorts a bit differently. Per recent gripe from Magnus.
-