- 05 5月, 2009 2 次提交
-
-
由 Tom Lane 提交于
volatility columns localizable.
-
由 Heikki Linnakangas 提交于
-
- 04 5月, 2009 10 次提交
-
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
to make sure that the error code is reset, as a precaution in case the API doesn't properly reset it on success. This could be necessary, since we check the error value even if the function doesn't fail for specific success cases.
-
由 Peter Eisentraut 提交于
tree with references to the appropriate URLs. Robert Haas
-
由 Tom Lane 提交于
-
由 Alvaro Herrera 提交于
whether it failed. Modelled after catcache.c's usage of DlList, per suggestion from Tom.
-
由 Tom Lane 提交于
Fujii Masao
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
a parenthetical remark.
-
由 Tom Lane 提交于
canonicalized. Avoid the need to elog(FATAL) on out-of-memory.
-
由 Tom Lane 提交于
-
- 03 5月, 2009 5 次提交
-
-
由 Tatsuo Ishii 提交于
Patch contributed by Chuck McDevitt
-
由 Tom Lane 提交于
error message if the installation directory layout is messed up (or at least, something more useful than the behavior exhibited in bug #4787). During postmaster startup, check that get_pkglib_path resolves as a readable directory; and if ParseTzFile() fails to open the expected timezone abbreviation file, check the possibility that the directory is missing rather than just the specified file. In case of either failure, issue a hint suggesting that the installation is broken. These two checks cover the lib/ and share/ trees of a full installation, which should take care of most scenarios where a sysadmin decides to get cute.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
as per my recent proposal. release.sgml itself is now just a stub that should change rarely; ideally, only once per major release to add a new include line. Most editing work will occur in the release-N.N.sgml files. To update a back branch for a minor release, just copy the appropriate release-N.N.sgml file(s) into the back branch. This commit doesn't change the end-product documentation at all, only the source layout. However, it makes it easy to start omitting ancient information from newer branches' documentation, should we ever decide to do that.
-
由 Tom Lane 提交于
never a BEGIN block. This is required for Oracle compatibility and is also plainly stated to be the behavior by our original documentation (up until 8.1, in which the docs were adjusted to match the code's behavior; but actually the old docs said the correct thing and the code was wrong). Not back-patched because this introduces an incompatibility that could break working applications. Requires release note.
-
- 02 5月, 2009 2 次提交
-
-
由 Tom Lane 提交于
failed to consider the possibility that it would get T_SCALAR, T_RECORD, or T_ROW instead because the word happens to match a plpgsql variable name. In particular, give "duplicate declaration" rather than generic "syntax error" if the same identifier is declared twice in the same block, as per my recent complaint. Also behave more sanely when decl_aliasitem or proc_condition or opt_lblname is coincidentally not T_WORD. Refactor the related productions a bit to reduce duplication. This is a longstanding bug, but it doesn't seem critical enough to back-patch.
-
由 Tom Lane 提交于
part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.9999999999999999999999999999", with the exact number of nines needed to cause failure varying depending on float-timestamp option and possibly on platform. Obviously this should round up to the next integral second, if we don't have enough precision to distinguish the value from that. Per bug #4789 from Robert Kruus. In passing, fix a missed check for fractional seconds in one copy of the "is it greater than 24:00:00" code. Broken all the way back, so patch all the way back.
-
- 30 4月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
leftover unused variables. Laurent Laborde
-
- 29 4月, 2009 3 次提交
-
-
由 Heikki Linnakangas 提交于
keyword lists in gram.y and kwlist.h. It checks that all lists are in alphabetical order, and that all keywords present in gram.y are listed in kwlist.h in the right category, and that all keywords in kwlist.h are also in gram.y. What's still missing is to check that all keywords defined with "%token <keyword>" in gram.y are present in one of the keyword lists in gram.y.
-
由 Tom Lane 提交于
PlaceHolderVar nodes in join quals appearing in or below the lowest outer join that could null the subquery being pulled up. This improves the planner's ability to recognize constant join quals, and probably helps with detection of common sort keys (equivalence classes) as well.
-
由 Bruce Momjian 提交于
-
- 28 4月, 2009 3 次提交
-
-
由 Heikki Linnakangas 提交于
-
由 Bruce Momjian 提交于
are already correct.
-
由 Bruce Momjian 提交于
and SQL).
-
- 27 4月, 2009 1 次提交
-
-
由 Tom Lane 提交于
apparently found uninteresting, and do minor wordsmithing on a number of the existing entries.
-
- 26 4月, 2009 4 次提交
-
-
由 Tom Lane 提交于
if there are any Windows configurations where port/win32.h fails to provide the macro, it should be fixed in the latter file not here.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
than having some whitespace discrepancy. Although whitespace is supposed to be ignored in our regression tests, for some reason buildfarm member spoonbill doesn't like it.
-
由 Tom Lane 提交于
aggregate function. By definition, such a sub-SELECT cannot reference any variables of query levels between itself and the aggregate's semantic level (else the aggregate would've been assigned to that lower level instead). So the correct, most efficient implementation is to treat the sub-SELECT as being a sub-select of that outer query level, not the level the aggregate syntactically appears in. Not doing so also confuses the heck out of our parameter-passing logic, as illustrated in bug report from Daniel Grace. Fortunately, we were already copying the whole Aggref expression up to the outer query level, so all that's needed is to delay SS_process_sublinks processing of the sub-SELECT until control returns to the outer level. This has been broken since we introduced spec-compliant treatment of outer aggregates in 7.4; so patch all the way back.
-
- 25 4月, 2009 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
- 24 4月, 2009 6 次提交
-
-
由 Magnus Hagander 提交于
and the old ones. Consistently talk about certificate verification, and not validation.
-
由 Magnus Hagander 提交于
used instead.
-
由 Magnus Hagander 提交于
"verify-ca" and "verify-full". Since "prefer" remains the default, this will make certificate validation off by default, which should lead to less upgrade issues.
-
由 Magnus Hagander 提交于
Per discussion.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
A service of your local coding style police.
-
- 23 4月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
and FSM.
-