- 03 2月, 2014 6 次提交
-
-
由 Robert Haas 提交于
Michael Paquier, reviewed by Christian Kruse
-
由 Andrew Dunstan 提交于
Craig Ringer.
-
由 Fujii Masao 提交于
The temporary statistics files don't need to be included in the backup because they are always reset at the beginning of the archive recovery. This patch changes pg_basebackup so that it skips all files located in $PGDATA/pg_stat_tmp or the directory specified by stats_temp_directory parameter.
-
由 Fujii Masao 提交于
-
由 Tom Lane 提交于
Remove unused copy-and-pasted macro definitions, and improve formatting of recently-added productions. I got interested in this because buildfarm member protosciurus has been crashing in "bison repl_gram.y" since commit 858ec118. It's a long shot that this will fix that, though maybe the missing trailing semicolon has something to do with it? In any case, there's no need to approve of dead code, nor of code whose formatting isn't even self-consistent let alone consistent with what's around it.
-
- 02 2月, 2014 8 次提交
-
-
由 Fujii Masao 提交于
-
由 Fujii Masao 提交于
Thom Brown
-
由 Andrew Dunstan 提交于
-
由 Tom Lane 提交于
In p_isdigit and other character class test functions generated by the p_iswhat macro, the code path for non-C locales with multibyte encodings contained a bogus pointer cast that would accidentally fail to malfunction if types wchar_t and wint_t have the same width. Apparently that is true on most platforms, but not on recent Cygwin releases. Remove the cast, as it seems completely unnecessary (I think it arose from a false analogy to the need to cast to unsigned char when dealing with the <ctype.h> functions). Per bug #8970 from Marco Atzeri. In the same functions, the code path for C locale with a multibyte encoding simply ANDed each wide character with 0xFF before passing it to the corresponding <ctype.h> function. This could result in false positive answers for some non-ASCII characters, so use a range test instead. Noted by me while investigating Marco's complaint. Also, remove some useless though not actually buggy maskings and casts in the hand-coded p_isalnum and p_isalpha functions, which evidently got tested a bit more carefully than the macro-generated functions.
-
由 Andrew Dunstan 提交于
-
由 Tom Lane 提交于
WalSndKill was doing things exactly backwards: it should first clear MyWalSnd (to stop signal handlers from touching MyWalSnd->latch), then disown the latch, and only then mark the WalSnd struct unused by clearing its pid field. Also, WalRcvSigUsr1Handler and worker_spi_sighup failed to preserve errno, which is surely a requirement for any signal handler. Per discussion of recent buildfarm failures. Back-patch as far as the relevant code exists.
-
由 Andrew Dunstan 提交于
The preferred method is to use "cc -shared", and this allows binaries to be rebased if required, unlike dllwrap. Backpatch to 9.0 where we have buildfarm coverage. There are still some issues with Cygwin, especially modern Cygwin, but this helps us get closer to good support. Marco Atzeri.
-
由 Andrew Dunstan 提交于
This has long been done by the MSVC build system, and has caused confusion in the past when programs like psql have failed to start because they can't find the DLL. If it's in the same directory as it now will be they will find it. Backpatch to all live branches.
-
- 01 2月, 2014 18 次提交
-
-
由 Bruce Momjian 提交于
Previously an input array string that started with a single-element array dimension would then later accept a multi-dimensional segment. BACKWARD INCOMPATIBILITY
-
由 Robert Haas 提交于
Replication slots are a crash-safe data structure which can be created on either a master or a standby to prevent premature removal of write-ahead log segments needed by a standby, as well as (with hot_standby_feedback=on) pruning of tuples whose removal would cause replication conflicts. Slots have some advantages over existing techniques, as explained in the documentation. In a few places, we refer to the type of replication slots introduced by this patch as "physical" slots, because forthcoming patches for logical decoding will also have slots, but with somewhat different properties. Andres Freund and Robert Haas
-
由 Bruce Momjian 提交于
Mentioned in substring() and regexp_replace() sections.
-
由 Bruce Momjian 提交于
per report from Josh Kupershmidt
-
由 Robert Haas 提交于
Evidence from buildfarm member crake suggests that the new test_shm_mq module is routinely crashing the server due to the arrival of a SIGUSR1 after the shared memory segment has been unmapped. Although processes using the new dynamic background worker facilities are more likely to receive a SIGUSR1 around this time, the problem is also possible on older branches, so I'm back-patching the parts of this change that apply to older branches as far as they apply. It's already generally the case that code checks whether these pointers are NULL before deferencing them, so the important thing is mostly to make sure that they do get set to NULL before they become invalid. But in master, there's one case in procsignal_sigusr1_handler that lacks a NULL guard, so add that. Patch by me; review by Tom Lane.
-
由 Bruce Momjian 提交于
Takayuki Tsunakawa
-
由 Bruce Momjian 提交于
Report from Jozef Mlich using Coverity
-
由 Bruce Momjian 提交于
Backpatch to 9.3 Adjusted patch from Ian Lawrence Barwick
-
由 Tom Lane 提交于
Commit 820f08ca claimed to make the server and libpq handle SSL protocol versions identically, but actually the server was still accepting SSL v3 protocol while libpq wasn't. Per discussion, SSL v3 is obsolete, and there's no good reason to continue to accept it. So make the code really equivalent on both sides. The behavior now is that we use the highest mutually-supported TLS protocol version. Marko Kreen, some comment-smithing by me
-
由 Bruce Momjian 提交于
Dean Rasheed
-
由 Tom Lane 提交于
Michael Paquier
-
由 Bruce Momjian 提交于
Suggested by David Tonhofer
-
由 Bruce Momjian 提交于
Document that FOR UPDATE/SHARE are incompatible with GROUP BY, DISTINCT, HAVING and window functions. Michael Paquier
-
由 Bruce Momjian 提交于
Report form Antonin Houska
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Allows typedefs to be specified on the command line, per request from Andrew.
-
由 Fujii Masao 提交于
-
由 Bruce Momjian 提交于
Add new entab options to process only C comment whitespace after periods, and to protect leading whitespace.
-
- 31 1月, 2014 8 次提交
-
-
由 Andrew Dunstan 提交于
Per gripe from hubert depesz lubaczewski. Also improve examples for this and json_array_elements so they match the example results.
-
由 Tom Lane 提交于
The buildfarm says commit 58274728 doesn't work so well on Windows. This is because the encoding part of Windows locale names can be just a code page number, eg "1252", which we don't consider to be a valid encoding name. Add a check to accept encoding parts that are case-insensitively string equal; this at least ensures that the new code doesn't reject any cases that the old code allowed.
-
由 Bruce Momjian 提交于
This requires a new version of pg_bsd_indent, version 1.3, to be downloaded.
-
由 Tom Lane 提交于
Even though the server tries to canonicalize stored locale names, the platform often doesn't cooperate, so it's entirely possible that one DB thinks its locale is, say, "en_US.UTF-8" while the other has "en_US.utf8". Rather than failing, we should try to allow this where it's clearly OK. There is already pretty robust encoding lookup in encnames.c, so make use of that to compare the encoding parts of the names. The locale identifier parts are just compared case-insensitively, which we were already doing. The major problem known to exist in the field is variant encoding-name spellings, so hopefully this will be Good Enough. If not, we can try being even laxer. Pavel Raiskup, reviewed by Rushabh Lathia
-
由 Tom Lane 提交于
Thinko in error report (and a typo in the message text, too). We're failing anyway, but it would be good to print something useful first. Noted while reviewing a patch to make pg_upgrade's locale code laxer.
-
由 Robert Haas 提交于
Vik Fearing, reviewed by Pavel Stehule and myself
-
由 Tom Lane 提交于
When pulling a "postponed" qual from a LATERAL subquery up into the quals of an outer join, we must make sure that the postponed qual is included in those seen by make_outerjoininfo(). Otherwise we might compute a too-small min_lefthand or min_righthand for the outer join, leading to "JOIN qualification cannot refer to other relations" failures from distribute_qual_to_rels. Subtler errors in the created plan seem possible, too, if the extra qual would only affect join ordering constraints. Per bug #9041 from David Leverton. Back-patch to 9.3.
-
由 Bruce Momjian 提交于
-