- 27 10月, 2004 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
index entries for IS-foo constructs.
-
由 Bruce Momjian 提交于
> * Allow TIMESTAMP WITH TIME ZONE to store the original timezone > information, either by name or offset from UTC
-
由 Bruce Momjian 提交于
Viktor Vislobokov
-
由 Tom Lane 提交于
in all cases when keep_buf = true. This allows ANALYZE's inner loop to use heap_release_fetch, which saves multiple buffer lookups for the same page and avoids overestimation of cost by the vacuum cost mechanism.
-
- 25 10月, 2004 16 次提交
-
-
由 Tom Lane 提交于
the parent table, it's essential that all index accesses take some kind of lock on the index. I had missed vacuumlazy.c :-( ...
-
由 Neil Conway 提交于
to RELEASE_CHANGES so that this is not forgotten in the future.
-
由 Neil Conway 提交于
pfree().
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
such as bug #1293.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
writing 'foo()' rather than 'foo(void)'.
-
由 Neil Conway 提交于
returning a NULL pointer (some callers remembered to check the return value, but some did not -- it is safer to just bail out). Also, cleanup pgstat.c to use elog(ERROR) rather than elog(LOG) followed by exit().
-
由 PostgreSQL Daemon 提交于
make sure we tag configure.in as beta4 as well ...
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Andrew Dunstan
-
由 Tom Lane 提交于
Andrew Dunstan
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 24 10月, 2004 5 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
a routine part of release prep.
-
由 Dennis Bjorklund 提交于
-
由 Tom Lane 提交于
compiler emits any warnings, the test program had better be 100% correct, not only 90% correct. The recent addition of -Wold-style-definition broke thread-safety detection on every platform that has that switch, because the test program used an old-style definition.
-
- 23 10月, 2004 12 次提交
-
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Magnus Hagander
-
由 Tom Lane 提交于
Magnus Hagander
-
由 Tom Lane 提交于
examinable by non-superusers, and use it to protect the recently-added GUC variables for data directory and config files. For now I have only flagged those variables that could be used to deduce something about the server's filesystem layout, but possibly we should also mark vars related to logging settings and other admin-only information?
-
由 Tom Lane 提交于
at the top level of the column's old default expression before adding an implicit coercion to the new column type. This seems to satisfy the principle of least surprise, as per discussion of bug #1290.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
- 22 10月, 2004 2 次提交
-
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-