- 19 3月, 2011 7 次提交
-
-
由 Magnus Hagander 提交于
Don't leave partial filename information on the last status or dangling characters if the previous filename was longer than the current one.
-
由 Bruce Momjian 提交于
-
由 Robert Haas 提交于
When adding an inheritance parent to a table, an AccessShareLock on the parent isn't strong enough to prevent trouble, so take ShareUpdateExclusiveLock instead. Since this is a behavior change, albeit a fairly unobtrusive one, and since we have only one report from the field, no back-patch. Report by Jon Nelson, analysis by Alvaro Herrera, fix by me.
-
由 Robert Haas 提交于
This is advantageous because the BG writer is alive until much later in the shutdown sequence than WAL writer; we want to make sure that it's possible to shut off synchronous replication during a smart shutdown, else it might not be possible to complete the shutdown at all. Per very reasonable gripes from Fujii Masao and Simon Riggs.
-
由 Robert Haas 提交于
Noted by Tom Lane.
-
由 Bruce Momjian 提交于
the time on the primary that the transaction was generated.
-
由 Bruce Momjian 提交于
-
- 18 3月, 2011 10 次提交
-
-
由 Robert Haas 提交于
Per a gripe from Thom Brown about my previous commit in this area, commit 9a56dc33.
-
由 Robert Haas 提交于
The last version in which these options were documented is now EOL, so it's time to get rid of them for real. We now use GNU-style long options instead.
-
由 Robert Haas 提交于
Without this, the startup process goes into a tight loop, consuming 100% of one CPU and failing to respond to interrupts.
-
由 Robert Haas 提交于
Erik Rijkers and me
-
由 Robert Haas 提交于
-
由 Robert Haas 提交于
-
由 Alvaro Herrera 提交于
Report and patch from Daniel Popowich, bug #5842 (with some debugging help from Alex Hunsaker)
-
由 Peter Eisentraut 提交于
The maximum value of deadlock_timeout, max_standby_archive_delay, max_standby_streaming_delay, log_min_duration_statement, and log_autovacuum_min_duration was INT_MAX/1000 milliseconds, which is about 35min, which is too short for some practical uses. Raise the maximum value to INT_MAX; the code that uses the parameters already supports that just fine.
-
由 Robert Haas 提交于
Fujii Masao, but with the proposed behavior change reverted, and the rest adjusted accordingly.
-
由 Robert Haas 提交于
1. Don't ignore query cancel interrupts. Instead, if the user asks to cancel the query after we've already committed it, but before it's on the standby, just emit a warning and let the COMMIT finish. 2. Don't ignore die interrupts (pg_terminate_backend or fast shutdown). Instead, emit a warning message and close the connection without acknowledging the commit. Other backends will still see the effect of the commit, but there's no getting around that; it's too late to abort at this point, and ignoring die interrupts altogether doesn't seem like a good idea. 3. If synchronous_standby_names becomes empty, wake up all backends waiting for synchronous replication to complete. Without this, someone attempting to shut synchronous replication off could easily wedge the entire system instead. 4. Avoid depending on the assumption that if a walsender updates MyProc->syncRepState, we'll see the change even if we read it without holding the lock. The window for this appears to be quite narrow (and probably doesn't exist at all on machines with strong memory ordering) but protecting against it is practically free, so do that. 5. Remove useless state SYNC_REP_MUST_DISCONNECT, which isn't needed and doesn't actually do anything. There's still some further work needed here to make the behavior of fast shutdown plausible, but that looks complex, so I'm leaving it for a separate commit. Review by Fujii Masao.
-
- 17 3月, 2011 3 次提交
-
-
由 Bruce Momjian 提交于
Tom Lane
-
由 Andrew Dunstan 提交于
This has been broken for years, and I'm not sure why it has not been noticed before, but now a very modern Cygwin breaks on it, and the fix is clearly correct. Backpatching to all live branches.
-
由 Robert Haas 提交于
Pavel Stehule
-
- 16 3月, 2011 7 次提交
-
-
由 Robert Haas 提交于
Omit incorrect = sign, and properly document server_name parameter. Shigeru Hanada
-
由 Tom Lane 提交于
This patch causes unknown-type Consts to be coerced to the resolved output type of the set operation at parse time. Formerly such Consts were left alone until late in the planning stage. The disadvantage of that approach is that it disables some optimizations, because the planner sees the set-op leaf query as having different output column types than the overall set-op. We saw an example of that in a recent performance gripe from Claudio Freire. Fixing such a Const requires scribbling on the leaf query in transformSetOperationTree, but that should be all right since if the leaf query's semantics depended on that output column, it would already have resolved the unknown to something else. Most of the bulk of this patch is a simple adjustment of transformSetOperationTree's API so that upper levels can get at the TargetEntry containing a Const to be replaced: it now returns a list of TargetEntries, instead of just the bare expressions.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Specifically, mention that "restart" is disabled by this parameter.
-
- 15 3月, 2011 5 次提交
-
-
由 Bruce Momjian 提交于
the comments on the template1 database. No catalog version bump because they are just comments.
-
由 Robert Haas 提交于
- Make the name of the ID tag for the GUC entry match the GUC name. - Clarify that synchronous_replication waits for xlog flush, not receipt. - Mention that synchronous_replication won't wait if max_wal_senders=0.
-
由 Robert Haas 提交于
Review by Tom Lane.
-
由 Magnus Hagander 提交于
This was required in pre-8.4 versions to allow the specification of "ident sameuser", but sameuser is no longer required. It could be extended to allow all parameters in the future, but should then apply to all methods and not just ident.
-
由 Tom Lane 提交于
We have a test that verifies that max(anyarray) will cope if the array column elements aren't all the same array type. However, it's now possible for that to produce a collation-related error message instead of the expected one, if the first two column elements happen to be of the same type and it's one that expects to be given collation info. Tweak the test to ensure this doesn't happen. Per buildfarm member pika.
-
- 14 3月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Its mechanism for recovering after deleting the current list cell was a bit klugy. Borrow the technique used in other places.
-
- 13 3月, 2011 1 次提交
-
-
由 Tom Lane 提交于
While this will give wrong answers when estimating selectivity for a comparison operator that's using a non-default collation, the estimation error probably won't be large; and anyway the former approach created estimation errors of its own by trying to use a histogram that might have been computed with some other collation. So we'll adopt this simplified approach for now and perhaps improve it sometime in the future. This patch incorporates changes from Andres Freund to make sure that selfuncs.c passes a valid collation OID to any datatype-specific function it calls, in case that function wants collation information. Said OID will now always be DEFAULT_COLLATION_OID, but at least we won't get errors.
-
- 12 3月, 2011 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
This isn't very important by itself, but was left on my list of things without test coverage for the collation feature.
-
由 Tom Lane 提交于
We previously heard of the same problem in int24div(), so there's not a good reason to suppose the problem is confined to cases involving int8.
-
由 Tom Lane 提交于
Add dummy returns before every potential division-by-zero in int8.c, because apparently further "improvements" in gcc's optimizer have enabled it to break functions that weren't broken before. Aurelien Jarno, via Martin Pitt
-