- 10 9月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
file handle on it, the file goes into "pending deletion" state where it still shows up in directory listing, but isn't accessible otherwise. That confuses RemoveOldXLogFiles(), making it think that the file hasn't been archived yet, while it actually was, and it was deleted along with the .done file. Fix that by renaming the file with ".deleted" extension before deleting it. Also check the return value of rename() and unlink(), so that if the removal fails for any reason (e.g another process is holding the file locked), we don't delete the .done file until the WAL file is really gone. Backpatch to 8.2, which is the oldest version supported on Windows.
-
- 08 9月, 2009 1 次提交
-
-
由 Tom Lane 提交于
It seems the flex developers have decided to change yyleng from int to size_t. This has already happened in the latest release of OS X, and will start happening elsewhere once the next release of flex appears. Rather than trying to divine how it's declared in any particular build, let's just remove the one existing not-very-necessary external usage. Back-patch to all supported branches; not so much because users in the field are likely to care about building old branches with cutting-edge flex, as to keep OSX-based buildfarm members from having problems with old branches.
-
- 06 9月, 2009 1 次提交
-
-
由 Tom Lane 提交于
to the Default timezone abbreviation set. Back-port the the current file set to all branches that contain tznames. This includes adding SGT to the Default set in pre-8.4 releases. Joachim Wieland
-
- 04 9月, 2009 6 次提交
-
-
由 Heikki Linnakangas 提交于
specify an encoding explicitly, we used to treat it as being in database encoding when we parsed it, but then perform a UTF-8 -> database encoding conversion on it, which was completely bogus. It's now consistently treated as UTF-8.
-
由 Marc G. Fournier 提交于
Tag 8.3.8
-
由 Tom Lane 提交于
7.4.26.
-
由 Tom Lane 提交于
to unload and re-load the library. The difficulty with unloading a library is that we haven't defined safe protocols for doing so. In particular, there's no safe mechanism for getting out of a "hook" function pointer unless libraries are unloaded in reverse order of loading. And there's no mechanism at all for undefining a custom GUC variable, so GUC would be left with a pointer to an old value that might or might not still be valid, and very possibly wouldn't be in the same place anymore. While the unload and reload behavior had some usefulness in easing development of new loadable libraries, it's of no use whatever to normal users, so just disabling it isn't giving up that much. Someday we might care to expend the effort to develop safe unload protocols; but even if we did, there'd be little certainty that every third-party loadable module was following them, so some security restrictions would still be needed. Back-patch to 8.2; before that, LOAD was superuser-only anyway. Security: unprivileged users could crash backend. CVE not assigned yet
-
由 Tom Lane 提交于
functions. This extends the previous patch that forbade SETting these variables inside security-definer functions. RESET is equally a security hole, since it would allow regaining privileges of the caller; furthermore it can trigger Assert failures and perhaps other internal errors, since the code is not expecting these variables to change in such contexts. The previous patch did not cover this case because assign hooks don't really have enough information, so move the responsibility for preventing this into guc.c. Problem discovered by Heikki Linnakangas. Security: no CVE assigned yet, extends CVE-2007-6600
-
由 Peter Eisentraut 提交于
-
- 03 9月, 2009 1 次提交
-
-
由 Tom Lane 提交于
Egypt, Mauritius, Bangladesh.
-
- 02 9月, 2009 1 次提交
-
-
由 Tom Lane 提交于
(could happen if either postgresql.conf or postmaster.opts is empty). It's been broken since the C version was written for 8.0, so patch all the way back. initdb's copy of the function is broken in the same way, but it's less important there since the input files should never be empty. Patch that in HEAD only, and also fix some cosmetic differences that crept into that copy of the function. Per report from Corry Haines and Jeff Davis.
-
- 31 8月, 2009 1 次提交
-
-
由 Tom Lane 提交于
One of these represents a nontrivial bug (a promptly-leaked palloc), so backpatch. Greg Stark
-
- 27 8月, 2009 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 25 8月, 2009 2 次提交
-
-
由 Alvaro Herrera 提交于
This causes problems when the system load is high, per report from Zdenek Kotala in <1250860954.1239.114.camel@localhost>; instead of calling kill directly, have the signal handler set a flag which is checked in ServerLoop. This way, the handler can return before being called again by a subsequent signal sent from the autovacuum launcher. Also, increase the sleep in the launcher in this failure path to 1 second. Backpatch to 8.3, which is when the signalling between autovacuum launcher/postmaster was introduced. Also, add a couple of ReleasePostmasterChildSlot calls in error paths; this part backpatched to 8.4 which is when the child slot stuff was introduced.
-
由 Tom Lane 提交于
#include the version of history.h that is in the same directory as the readline.h we are using. This avoids problems in some scenarios where both readline and editline are installed. Report and patch by Zdenek Kotala.
-
- 19 8月, 2009 1 次提交
-
-
由 Tom Lane 提交于
and integer datetimes are in use. Per bug report from Hubert Depesz Lubaczewski. Alex Hunsaker
-
- 17 8月, 2009 2 次提交
-
-
由 Tom Lane 提交于
This was changed in 8.2 but the documentation was not corrected. Per gripe from Sam Mason.
-
由 Tom Lane 提交于
truncate_identifier won't do anything if the passed-in strlen is already less than NAMEDATALEN, which it always would be given the strlcpy usage. This has been broken since the arrays-of-composite-types code went in. Arguably truncate_identifier is suffering from excessive optimization and should always process the string, but for the moment I'll take the more localized patch. Per bug #4987.
-
- 16 8月, 2009 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 8月, 2009 1 次提交
-
-
由 Tom Lane 提交于
to access a Relation entry it had just closed. I happened to be testing with CLOBBER_CACHE_ALWAYS, which made this a guaranteed core dump (at least on machines where sprintf %s isn't forgiving of a NULL pointer). It's probably quite unlikely that it would fail in the field, but a bug is a bug. Fix by moving the relation_close call down past the logging action.
-
- 11 8月, 2009 1 次提交
-
-
由 Magnus Hagander 提交于
that memory allocated by starting third party DLLs doesn't end up conflicting with it. Hopefully this solves the long-time issue with "could not reattach to shared memory" errors on Win32. Patch from Tsutomu Yamada and me, based on idea from Trevor Talbot.
-
- 10 8月, 2009 2 次提交
-
-
由 Magnus Hagander 提交于
affects the C compiler step - we still only build one target at a time.
-
由 Andrew Dunstan 提交于
Re-add documentation for --no-readline option of psql, mistakenly removed a decade ago. Backpatch to release 7.4.
-
- 08 8月, 2009 1 次提交
-
-
由 Tom Lane 提交于
when we reach the post-COPY "pump it dry" error recovery code that was added 2006-11-24. Per a report from Neil Best, there is at least one code path in which this occurs, leading to an infinite loop in code that's supposed to be making it more robust not less so. A reasonable response seems to be to call PQputCopyEnd() again, so let's try that. Back-patch to all versions that contain the cleanup loop.
-
- 07 8月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
if a smart shutdown is already in progress. Backpatch to 8.3, this was broken in the patch that introduced "dead-end backends". Per report by Itagaki Takahiro, patch by Fujii Masao.
-
- 30 7月, 2009 1 次提交
-
-
由 Magnus Hagander 提交于
header files. Josh Williams
-
- 29 7月, 2009 1 次提交
-
-
由 Tom Lane 提交于
we should ignore NULL array entries, not non-NULL ones. This had the effect of disabling commit_delay, and could have caused a crash in the rare race condition the patch was intended to fix. Bug report and diagnosis by Jeff Janes, in bug #4952.
-
- 28 7月, 2009 1 次提交
-
-
由 Teodor Sigaev 提交于
Aaron Marcuse-Kubitza <aaronmk@blackducksoftware.com>
-
- 25 7月, 2009 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 21 7月, 2009 1 次提交
-
-
由 Alvaro Herrera 提交于
The original coding was not dealing specially with this file being a symlink, with the end result that it was not installed in VPATH builds. Oddly enough, the clean target does know about it ...
-
- 18 7月, 2009 1 次提交
-
-
由 Tom Lane 提交于
that the sanity checking I added to create_mergejoin_plan() in 8.3 was a few bricks shy of a load: the mergeclauses could reference pathkeys in a noncanonical order such as x,y,x, not only cases like x,x,y which is all that the code had allowed for. The odd cases only turn up when using redundant clauses in an outer join condition, which is why no one had noticed before.
-
- 14 7月, 2009 1 次提交
-
-
由 Tom Lane 提交于
RevalidateCachedPlan. This is to avoid a "SPI_ERROR_CONNECT" failure when the planner calls a SPI-using function and we are already inside one. The alternative fix is to expect callers of RevalidateCachedPlan to do this, which seems likely to result in additional hard-to-detect bugs of omission. Per reports from Frank van Vugt and Marek Lewczuk. Back-patch to 8.3. It's much harder to trigger the bug in 8.3, due to a smaller set of cases in which plans can be invalidated, but it could happen. (I think perhaps only a SI reset event could make 8.3 fail here, but that's certainly within the realm of possibility.)
-
- 10 7月, 2009 1 次提交
-
-
由 Tom Lane 提交于
last pair of parameter name/value strings, even when there are MAXPARAMS of them. Aboriginal bug in contrib/xml2, noted while studying bug #4912 (though I'm not sure whether there's something else involved in that report). This might be thought a security issue, since it's a potential backend crash; but considering that untrustworthy users shouldn't be allowed to get their hands on xslt_process() anyway, it's probably not worth getting excited about.
-
- 07 7月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
In what seems like an oversight, we used to treat 'TH' the same as lowercase 'th', but only with HH/HH12.
-
- 25 6月, 2009 1 次提交
-
-
由 Magnus Hagander 提交于
we already do it for PAM.
-
- 24 6月, 2009 1 次提交
-
-
由 Tom Lane 提交于
a number of other geometric operators also depend on. It miscalculated the slope of the perpendicular to the given line segment anytime that slope was other than 0, infinite, or +/-1. In some cases the error would be masked because the true closest point on the line segment was one of its endpoints rather than the intersection point, but in other cases it could give an arbitrarily bad answer. Per bug #4872 from Nick Roosevelt. Bug goes clear back to Berkeley days, so patch all supported branches. Make a couple of cosmetic adjustments while at it.
-
- 18 6月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
-
- 14 6月, 2009 1 次提交
-
-
由 Tom Lane 提交于
This prevents autovacuum from reclaiming free space in them and causing the test's output row order to change, which is causing intermittent bogus failure reports in the buildfarm. Backpatch to 8.3. The issue exists further back, but since autovacuum was not on by default before 8.3, it's not a problem for buildfarm testing.
-
- 12 6月, 2009 1 次提交
-
-
由 Tom Lane 提交于
Bangladesh, Egypt, Jordan, Pakistan.
-
- 11 6月, 2009 1 次提交
-
-
由 Peter Eisentraut 提交于
-