- 01 6月, 2013 5 次提交
-
-
由 Stephen Frost 提交于
Fix a few spelling mistakes. Per bug report #8193 from Lajos Veres.
-
由 Stephen Frost 提交于
Make slightly better decisions about indentation than what pgindent is capable of. Mostly breaking out long function calls into one line per argument, with a few other minor adjustments. No functional changes- all whitespace. pgindent ran cleanly (didn't change anything) after. Passes all regressions.
-
由 Peter Eisentraut 提交于
They no longer match reality with the web site style sheets, and it is difficult to keep the up to date in a CSS world.
-
由 Noah Misch 提交于
Dean Rasheed
-
由 Peter Eisentraut 提交于
-
- 31 5月, 2013 3 次提交
-
-
由 Peter Eisentraut 提交于
Ian Lawrence Barwick
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
- 30 5月, 2013 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
This is the first run of the Perl-based pgindent script. Also update pgindent instructions.
-
- 29 5月, 2013 2 次提交
-
-
由 Robert Haas 提交于
Tomas Vondra
-
由 Bruce Momjian 提交于
-
- 27 5月, 2013 1 次提交
-
-
由 Stephen Frost 提交于
The documentation for ALTER TYPE .. RENAME claimed to support a RESTRICT/CASCADE option at the 'type' level, which wasn't implemented and doesn't make a whole lot of sense to begin with. What is supported, and previously undocumented, is ALTER TYPE .. RENAME ATTRIBUTE .. RESTRICT/CASCADE. I've updated the documentation and back-patched this to 9.1 where it was first introduced.
-
- 24 5月, 2013 1 次提交
-
-
由 Heikki Linnakangas 提交于
We're not installing it anymore. Michael Paquier
-
- 23 5月, 2013 2 次提交
-
-
由 Robert Haas 提交于
Pavan Deolasee
-
由 Heikki Linnakangas 提交于
When COPY uses the multi-insert method to insert a batch of tuples into the heap at a time, incorrect line number was printed if something went wrong in inserting the index tuples (primary key failure, for exampl), or processing after row triggers. Fixes bug #8173 reported by Lloyd Albin. Backpatch to 9.2, where the multi- insert code was added.
-
- 22 5月, 2013 3 次提交
-
-
由 Bruce Momjian 提交于
Per suggestion from Tom Lane.
-
由 Simon Riggs 提交于
Not necessary for correctness, just to make log_checkpoints output look less singular. Requested by Fujii Masao
-
由 Simon Riggs 提交于
checkpointer needs to reset ThisTimeLineID after a restartpoint to allow installing/recycling new WAL files. If recovery has already ended this would leave ThisTimeLineID set incorrectly and so we must reset it otherwise later checkpoints do not have the correct timeline. Bug report by Heikki Linnakangas. Further investigation by Heikki and myself.
-
- 21 5月, 2013 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Patch from Joe Abbate.
-
由 Peter Eisentraut 提交于
-
由 Heikki Linnakangas 提交于
In the primary_conninfo line that "pg_basebackup -R" generates, single quotes in parameter values need to be escaped into \\'; the libpq parser requires the quotes to be escaped into \', and recovery.conf parser requires the \ to be escaped into \\. Also, don't quote parameter values unnecessarily, to make the connection string prettier. Most options in a libpq connection string don't need quoting. Reported by Hari Babu, closer analysis by Zoltan Boszormenyi, although I didn't use his patch.
-
- 20 5月, 2013 3 次提交
-
-
由 Tom Lane 提交于
Clarify that this option doesn't suppress measurement of the statement's total runtime. Greg Smith
-
由 Simon Riggs 提交于
This simplifies the handling of crashes after fast promotion and various minor cases that can exist in short timing windows around that case. Broad fix to bug reported by Michael Paquier on -hackers, approach prompted by Heikki Linnakangas
-
由 Simon Riggs 提交于
-
- 19 5月, 2013 2 次提交
-
-
由 Simon Riggs 提交于
Michael Paquier
-
由 Heikki Linnakangas 提交于
euc_* and mule_internal test cases were identical to the ones in src/test/mb. sql_ascii didn't exist elsewhere, but has been broken since 2001, and doesn't seem very interesting anyway. drop.sql hasn't been used since 2000, when regress.sh was removed.
-
- 18 5月, 2013 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 17 5月, 2013 3 次提交
-
-
由 Tom Lane 提交于
PathNameOpenFile failed to ensure that the correct value of errno was returned to its caller after a failure (because it incorrectly supposed that free() can never change errno). In some cases this would result in a user-visible failure because an expected ENOENT errno was replaced with something else. Bogus EINVAL failures have been observed on OS X, for example. There were also a couple of places that could mangle an important value of errno if FDDEBUG was defined. While the usefulness of that debug support is highly debatable, we might as well make it safe to use, so add errno save/restore logic to the DO_DB macro. Per bug #8167 from Nelson Minar, diagnosed by RhodiumToad. Back-patch to all supported branches.
-
由 Tom Lane 提交于
If we're going to quote a well-known pangram, we should quote it accurately. Per gripe from Thom Brown.
- 16 5月, 2013 1 次提交
-
-
由 Tom Lane 提交于
The behavior is that the required sequence is created locally, which is appropriate because the default expression will be evaluated locally. Per gripe from Brad Nicholson that this case was refused with a confusing error message. We could have improved the error message but it seems better to just allow the case. Also, remove ALTER TABLE's arbitrary prohibition against being applied to foreign tables, which was pretty inconsistent considering we allow it for views, sequences, and other relation types that aren't even called tables. This is needed to avoid breaking pg_dump, which sometimes emits column defaults using separate ALTER TABLE commands. (I think this can happen even when the default is not associated with a sequence, so that was a pre-existing bug once we allowed column defaults for foreign tables.)
-
- 15 5月, 2013 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 14 5月, 2013 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
If OID wraparound should occur while in standalone mode (unlikely but possible), we want to advance the counter to FirstNormalObjectId not FirstBootstrapObjectId. Otherwise, user objects might be created with OIDs in the system-reserved range. That isn't immediately harmful but it poses a risk of conflicts during future pg_upgrade operations. Noted by Andres Freund. Back-patch to all supported branches, since all of them are supported sources for pg_upgrade operations.
-
- 13 5月, 2013 1 次提交
-
-
由 Tom Lane 提交于
In a construct like "select plain_function(set_returning_function(...))", the plain function is applied to each output row of the SRF successively. If some of the SRF outputs are NULL, and the plain function is strict, you'd expect to get NULL results for such rows ... but what actually happened was that such rows were omitted entirely from the result set. This was due to confusion of this case with what should happen for nested set-returning functions; a strict SRF is indeed supposed to yield an empty set for null input. Per bug #8150 from Erwin Brandstetter. Although this has been broken forever, we're not back-patching because of the possibility that some apps out there expect the incorrect behavior. This change should be listed as a possible incompatibility in the 9.3 release notes.
-
- 12 5月, 2013 1 次提交
-
-
由 Peter Eisentraut 提交于
-