- 24 10月, 2004 4 次提交
-
-
由 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 14 次提交
-
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Neil Conway 提交于
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Neil Conway 提交于
well be declared to return "void" to save callers the trouble of checking for errors.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
owned by postgres, doing "pg_ctl start" as root could allow a privilege escalation attack, as pointed out by iDEFENSE. Of course the postmaster would fail, but we ought to fail a little sooner to protect sysadmins unfamiliar with Postgres. The chosen fix is to disable root use of pg_ctl in all cases, just to be confident there are no other holes.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
NO ACTION check is deferrable. This seems to be a closer approximation to what the SQL spec says than what we were doing before, and it prevents some anomalous behaviors that are possible now that triggers can fire during the execution of PL functions. Stephan Szabo.
-
由 Tom Lane 提交于
any possible problems from child programs executed by the client app. Per suggestion from Elliot Lee of Red Hat.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
getting rid of numerous ad-hoc versions that have popped up in various places. Shortens code and avoids conflict with Windows min() and max() macros.
-
- 21 10月, 2004 2 次提交
- 20 10月, 2004 1 次提交
-
-
由 Neil Conway 提交于
-O2 -Wall -Wmissing-prototypes -Wpointer-arith Check whether the version of GCC we are using supports any of: -Wdeclaration-after-statement -Wendif-labels -Wold-style-definition And add the supported flags to CFLAGS.
-
- 19 10月, 2004 7 次提交
-
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
an oversize message, per suggestion from Oliver Jowett. I'm a bit dubious that this is a real problem, since the client likely doesn't have any more space available than the server, but it's not hard to make it behave according to the protocol intention.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
translation work.
-
由 Peter Eisentraut 提交于
-