- 09 5月, 2001 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
=================== In Notes: Refer to CREATE FUNCTION for information on creating aggregate functions. ^^^^^^^^^^^^^^^^^^^ I assume it must read C function instead. In Compatibility SQL/PSM: SQL/PSM is a proposed standard. We had that before: remove proposed. drop_index.sgml: ================ <REFNAME>: Removes existing indexes from a database as far as I can see index should be singular. The command description is written as if only one index can be removed at a time. Interestingly enough, in v7.0.2 it was in fact singular. Am I mistaken here? drop_operator.sgml: =================== In Outputs the arguments are referred to as type and type2, but the synopsis and Inputs section these are left_type and right_type, respectively. Also, oper is used in Outputs versus id in Inputs/Synopsis. In the translation I follow the replaceables used in the Inputs/Synopsis part. Frank Wegmann
-
由 Bruce Momjian 提交于
=================== In Notes: Refer to CREATE FUNCTION for information on creating aggregate functions. ^^^^^^^^^^^^^^^^^^^ I assume it must read C function instead. Frank Wegmann
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 08 5月, 2001 18 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
that doesn't actually work.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
passed, which occurs when no rows are retrieved by a SELECT. Mea maxima culpa ... I should have caught this.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
set null/default).
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> cronjob: > NOTICE: RegisterSharedInvalid: SI buffer overflow > NOTICE: InvalidateSharedInvalid: cache state reset > I don't understand what these mean. Should I be concerned about them > and what do they signify? No real need to worry. Those should've been downgraded to DEBUG-level messages a release or two back, but nobody bothered... Tom Lane
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 07 5月, 2001 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
a separate statement (though it can still be invoked as part of VACUUM, too). pg_statistic redesigned to be more flexible about what statistics are stored. ANALYZE now collects a list of several of the most common values, not just one, plus a histogram (not just the min and max values). Random sampling is used to make the process reasonably fast even on very large tables. The number of values and histogram bins collected is now user-settable via an ALTER TABLE command. There is more still to do; the new stats are not being used everywhere they could be in the planner. But the remaining changes for this project should be localized, and the behavior is already better than before. A not-very-related change is that sorting now makes use of btree comparison routines if it can find one, rather than invoking '<' twice.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
- 06 5月, 2001 1 次提交
-
-
由 Marc G. Fournier 提交于
not sure about this one ... but should have changelog in both versions ...
-
- 05 5月, 2001 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
configuration parameters in chapter 3.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
going to have any at all.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
running deferred triggers. They are really part of the regular transaction, and they could take awhile.
-
- 04 5月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
routine DetermineLocalTimeZone(). In that routine, be more wary of broken mktime() implementations than the original code was: don't allow mktime to change the already-set y/m/d/h/m/s information, and don't use tm_gmtoff if mktime failed. Possibly this will resolve some of the complaints we've been hearing from users of Middle Eastern timezones on RedHat.
-