Correctifs appliqués

Heikki Linnakangas a poussé :

  • Validate xlog record header before enlarging the work area to store it. If the record header is garbled, we're now quite likely to notice it before we try to make a bogus memory allocation and run out of memory. That can still happen, if the xlog record is split across pages (we cannot verify the record header until reading the next page in that scenario), but this reduces the chances. An out-of-memory is treated as a corrupt record anyway, so this isn't a correctness issue, just a case of giving a better error message. Per Amit Kapila's suggestion. http://git.postgresql.org/pg/commitdiff/567787f216da750b3805aea6fd8aef19e8b882a1
  • Fix mapping of PostgreSQL encodings to Python encodings. Windows encodings, "win1252" and so forth, are named differently in Python, like "cp1252". Also, if the PyUnicode_AsEncodedString() function call fails for some reason, use a plain ereport(), not a PLy_elog(), to report that error. That avoids recursion and crash, if PLy_elog() tries to call PLyUnicode_Bytes() again. This fixes bug reported by Asif Naeem. Backpatch down to 9.0, before that plpython didn't even try these conversions. Jan Urbański, with minor comment improvements by me. http://git.postgresql.org/pg/commitdiff/b66de4c6d7208d9ec420b912758377a3533c7a7d
  • Revert part of the previous patch that avoided using PLy_elog(). That caused the plpython_unicode regression test to fail on SQL_ASCII encoding, as evidenced by the buildfarm. The reason is that with the patch, you don't get the detail in the error message that you got before. That detail is actually very informative, so rather than just adjust the expected output, let's revert that part of the patch for now to make the buildfarm green again, and figure out some other way to avoid the recursion of PLy_elog() that doesn't lose the detail. http://git.postgresql.org/pg/commitdiff/de479e2ed28925ddd2907cad3e2d5dddd3b97199

Robert Haas a poussé :

Bruce Momjian a poussé :

Alvaro Herrera a poussé :

Tom Lane a poussé :

  • Improve documentation about MULE encoding. This commit improves the comments in pg_wchar.h and creates #define symbols for some formerly hard-coded values. No substantive code changes. Tatsuo Ishii and Tom Lane http://git.postgresql.org/pg/commitdiff/09022de1f55708bcfe8b2bf206d818055c34d49e
  • Remove support for using wait3() in place of waitpid(). All Unix-oid platforms that we currently support should have waitpid(), since it's in V2 of the Single Unix Spec. Our git history shows that the wait3 code was added to support NextStep, which we officially dropped support for as of 9.2. So get rid of the configure test, and simplify the macro spaghetti in reaper(). Per suggestion from Fujii Masao. http://git.postgresql.org/pg/commitdiff/fc548b2296df3fe039bf68e196bfd883338e0faa
  • Don't try to trim "../" in join_path_components(). join_path_components() tried to remove leading ".." components from its tail argument, but it was not nearly bright enough to do so correctly unless the head argument was (a) absolute and (b) canonicalized. Rather than try to fix that logic, let's just get rid of it: there is no correctness reason to remove "..", and cosmetic concerns can be taken care of by a subsequent canonicalize_path() call. Per bug #6715 from Greg Davidson. Back-patch to all supported branches. It appears that pre-9.2, this function is only used with absolute paths as head arguments, which is why we'd not noticed the breakage before. However, third-party code might be expecting this function to work in more general cases, so it seems wise to back-patch. In HEAD and 9.2, also make some minor cosmetic improvements to callers. http://git.postgresql.org/pg/commitdiff/85254199478bcf49d0ac83fdf22d6bcf35ceccb1
  • Simplify and document regex library's compact-NFA representation. The previous coding abused the first element of a cNFA state's arcs list to hold a per-state flag bit, which was confusing, undocumented, and not even particularly efficient. Get rid of that in favor of a separate "stflags" vector. Since there's only one bit in use, I chose to allocate a char per state; we could possibly replace this with a bitmap at some point, but that would make accesses a little slower. It's already about 8X smaller than before, so let's not get overly tense. Also document the representation better than it was before, which is to say not at all. This patch is a byproduct of investigations towards extracting a "fixed prefix" string from the compact-NFA representation of regex patterns. Might need to back-patch it if we decide to back-patch that fix, but for now it's just code cleanup so I'll just put it in HEAD. http://git.postgresql.org/pg/commitdiff/c6aae3042be5249e672b731ebeb21875b5343010
  • Fix planner to pass correct collation to operator selectivity estimators. We can do this without creating an API break for estimation functions by passing the collation using the existing fmgr functionality for passing an input collation as a hidden parameter. The need for this was foreseen at the outset, but we didn't get around to making it happen in 9.1 because of the decision to sort all pg_statistic histograms according to the database's default collation. That meant that selectivity estimators generally need to use the default collation too, even if they're estimating for an operator that will do something different. The reason it's suddenly become more interesting is that regexp interpretation also uses a collation (for its LC_TYPE not LC_COLLATE property), and we no longer want to use the wrong collation when examining regexps during planning. It's not that the selectivity estimate is likely to change much from this; rather that we are thinking of caching compiled regexps during planner estimation, and we won't get the intended benefit if we cache them with a different collation than the executor will use. Back-patch to 9.1, both because the regexp change is likely to get back-patched and because we might as well get this right in all collation-supporting branches, in case any third-party code wants to rely on getting the collation. The patch turns out to be minuscule now that I've done it ... http://git.postgresql.org/pg/commitdiff/e7ef6d7e248cd39b8a4a7630776ec3924feeafa6

Magnus Hagander a poussé :

Correctifs rejetés (à ce jour)

  • Pas de déception cette semaine :-)

Correctifs en attente

  • Alvaro Herrera and Zoltan Boszormenyi traded patches for the timeout framework and lock_timeout, which depends on same.
  • Kyotaro HORIGUCHI sent in two different revisions of a patch to fix an infelicity in PL/Perl's handling of UTF-8 in SQL_ASCII-encoded databases.
  • Hans-Juergen Schoenig sent in a rebased patch to add Bloom filters.
  • Dimitri Fontaine and Robert Haas exchanged a flurry of patches implementing event triggers.
  • Joel Jacobson sent in three revisions of a patch to output overloaded functions in deterministic order in pg_dump.
  • Pavel Stehule and Peter Geoghegan traded patches to enhance error fields.
  • Alvaro Herrera sent in another revision of the patch to implement foreign key locks.
  • Fujii Masao sent in a patch which removes support for using wait3() in place of waitpid(). No currently used system needs it.
  • Peter Eisentraut sent in another revision of the patch to implement TRANSFORMs.
  • Pavel Stehule sent in two more revisions of the code to allow using parameters in PL/pgsql DO blocks.
  • Satoshi Nagayasu sent in two revisions of a patch to add functions to get and reset statistics of WAL buffer writes (flushes) caused by the WAL buffer's becoming full.
  • Tom Lane sent in a patch to fix the issues in regex_fixed_prefix() by compiling the regex using the regex library and then looking at the compiled NFA representation to see if there must be a fixed prefix.