- 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 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
node starts from the same place as the first scan did. This avoids surprising behavior of scrollable and WITH HOLD cursors, as seen in Mark Kirkwood's bug report of yesterday. It's not entirely clear whether a rescan should be forced to drop out of the syncscan mode, but for the moment I left the code behaving the same on that point. Any change there would only be a performance and not a correctness issue, anyway. Back-patch to 8.3, since the unstable behavior was created by the syncscan patch.
-
由 Tom Lane 提交于
eg Japan. Report and fix by Itagaki Takahiro. Also fix CASHDEBUG printout format for branches with 64-bit money type, and some minor comment cleanup. Back-patch to 7.4, because it's broken all the way back.
-
- 10 6月, 2009 3 次提交
-
-
由 Tom Lane 提交于
Sergey Burladyan, there are at least some dank corners of libxml2 that assume this behavior, even though their published documentation suggests they shouldn't. This is only really a live problem in 8.3, but the code is still there for possible debugging use in HEAD, so patch both branches.
-
由 Alvaro Herrera 提交于
-
由 Alvaro Herrera 提交于
the database list too often. Per bug report from Łukasz Jagiełło and ensuing discussion on pgsql-performance.
-
- 09 6月, 2009 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 06 6月, 2009 3 次提交
-
-
由 Andrew Dunstan 提交于
Adjust recent PERL_SYS_INIT3 call to avoid platforms where it might fail, and to remove compilation warning. Backpatch the release 7.4
-
由 Tom Lane 提交于
should use GinItemPointerGetBlockNumber/GinItemPointerGetOffsetNumber, not ItemPointerGetBlockNumber/ItemPointerGetOffsetNumber, because the latter will Assert() on ip_posid == 0, ie a "Min" pointer. (Thus, ItemPointerIsMin has never worked at all, but it seems unused at present.) I'm not certain that the case can occur in normal functioning, but it's blowing up on me while investigating Tatsuo-san's data corruption problem. In any case it seems like a problem waiting to bite someone. Back-patch just in case this really is a problem for somebody in the field.
-
由 Andrew Dunstan 提交于
Search for versioned perl library instead of using hardcoded name on Windows. Backpatch to release 8.3
-
- 05 6月, 2009 1 次提交
-
-
由 Andrew Dunstan 提交于
-
- 02 6月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
symbolic links with the -l option, and as Fujii Masao pointed out we ended up overwriting files in the archive directory before this patch. Patch by Aidan Van Dyk, Fujii Masao and me. Backpatch to 8.3, where pg_standby was introduced.
-
- 25 5月, 2009 1 次提交
-
-
由 Tom Lane 提交于
this case is worth a special code path, but a special code path that gets the boundary condition wrong is definitely no good. Per bug #4821 from Andrew Gierth. In passing, clean up some minor code formatting issues (excess parentheses and blank lines in odd places). Back-patch to 8.3, where the bug was introduced.
-
- 19 5月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
there's no analyzable attributes or indexes. We also used to report 0 live and dead tuples for such tables, which messed with autovacuum threshold calculations. This fixes bug #4812 reported by George Su. Backpatch back to 8.1.
-
- 13 5月, 2009 1 次提交
-
-
由 Tom Lane 提交于
xml_parse, all arising from the same sloppy usage of parse_xml_decl. The original coding had that function returning its output string parameters in the libxml context, which is long-lived, and all but one of its callers neglected to free the strings afterwards. The easiest and most bulletproof fix is to return the strings in the local palloc context instead, since that's short-lived. This was only costing a dozen or two bytes per function call, but that adds up fast if the function is called repeatedly ... Noted while poking at the more general problem of what to do with our libxml memory allocation hooks. Back-patch to 8.3, which has the identical coding.
-
- 12 5月, 2009 1 次提交
-
-
由 Tom Lane 提交于
of AND/OR clause branches that predtest.c would attempt to deal with. As noted in bug #4721, that change disabled proof attempts for sizes of problems that people are actually expecting it to work for. The original complaint it was trying to solve was O(N^2) behavior for long IN-lists, so let's try applying the limit to just ScalarArrayOpExprs rather than everything. Another case of "foolish consistency" I fear. Back-patch to 8.2, same as the previous patch was.
-
- 07 5月, 2009 1 次提交
-
-
由 Heikki Linnakangas 提交于
you can end up with an unrecoverable backup if you start a new base backup right after finishing archive recovery. In that scenario, the redo pointer of the checkpoint that pg_start_backup() writes points to the XLOG segment where the timeline-changing end-of-archive-recovery checkpoint is. The beginning of that segment contains pages with the old timeline ID, and we don't accept that in recovery unless we find a history file covering the old timeline ID. If you omit pg_xlog from the base backup and clear the archive directory before starting the backup, there will be no such history file available. The bug is present in all versions since PITR was introduced in 8.0, but I'm back-patching only back to 8.2. Earlier versions didn't have XLOG switch records, making this fix unfeasible. Given the lack of reports until now, it doesn't seem worthwhile to spend more effort to fix 8.0 and 8.1. Per report and suggestion by Mikael Krantz
-
- 05 5月, 2009 1 次提交
-
-
由 Magnus Hagander 提交于
it fails because the shared memory segment already exists. This means it can take up to 10 seconds before it reports the error if it *does* exist, but hopefully it will make the system capable of restarting even when the server is under high load.
-
- 04 5月, 2009 2 次提交
-
-
由 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.
-
由 Tom Lane 提交于
Fujii Masao
-
- 03 5月, 2009 1 次提交
-
-
由 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.
-