- 22 3月, 2011 1 次提交
-
-
由 Tom Lane 提交于
Instead of playing cute games with pathkeys, just build a direct representation of the intended sub-select, and feed it through query_planner to get a Path for the index access. This is a bit slower than 9.1's previous method, since we'll duplicate most of the overhead of query_planner; but since the whole optimization only applies to rather simple single-table queries, that probably won't be much of a problem in practice. The advantage is that we get to do the right thing when there's a partial index that needs the implicit IS NOT NULL clause to be usable. Also, although this makes planagg.c be a bit more closely tied to the ordering of operations in grouping_planner, we can get rid of some coupling to lower-level parts of the planner. Per complaint from Marti Raudsepp.
-
- 21 3月, 2011 8 次提交
-
-
由 Heikki Linnakangas 提交于
ensure that they use different checkpoints as the starting point. We use the checkpoint redo location as a unique identifier for the base backup in the end-of-backup record, and in the backup history file name. Bug spotted by Fujii Masao.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
There's a lot we can't test very well without platform dependencies, but the C/POSIX collations should now work the same way everywhere.
-
由 Tom Lane 提交于
The local variable "sock" can be unused depending on compilation flags. But there seems no particular need for it, since the kernel calls can just as easily say port->sock instead.
-
由 Tom Lane 提交于
Install just one instance of the "C" and "POSIX" collations into pg_collation, rather than one per encoding. Make these instances exist and do something useful even in machines without locale_t support: to wit, it's now possible to force comparisons and case-folding functions to use C locale in an otherwise non-C database, whether or not the platform has support for using any additional collations. Fix up severely broken upper/lower/initcap functions, too: the C/POSIX fastpath now does what it is supposed to, and non-default collations are handled correctly in single-byte database encodings. Merge the two separate collation hashtables that were being maintained in pg_locale.c, and be more wary of the possibility that we fail partway through filling a cache entry.
-
- 20 3月, 2011 8 次提交
-
-
由 Bruce Momjian 提交于
notes. Remove excessive linking to pg_ctl manual page. Reorder incompatibility sections.
-
由 Magnus Hagander 提交于
Thom Brown
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
All expression nodes now have an explicit output-collation field, unless they are known to only return a noncollatable data type (such as boolean or record). Also, nodes that can invoke collation-aware functions store a separate field that is the collation value to pass to the function. This avoids confusion that arises when a function has collatable inputs and noncollatable output type, or vice versa. Also, replace the parser's on-the-fly collation assignment method with a post-pass over the completed expression tree. This allows us to use a more complex (and hopefully more nearly spec-compliant) assignment rule without paying for it in extra storage in every expression node. Fix assorted bugs in the planner's handling of collations by making collation one of the defining properties of an EquivalenceClass and by converting CollateExprs into discardable RelabelType nodes during expression preprocessing.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Magnus Hagander 提交于
This removes an overloading of two authentication options where one is very secure (peer) and one is often insecure (ident). Peer is also the name used in libpq from 9.1 to specify the same type of authentication. Also make initdb select peer for local connections when ident is chosen, and ident for TCP connections when peer is chosen. ident keyword in pg_hba.conf is still accepted and maps to peer authentication.
-
- 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 3 次提交
-
-
由 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 提交于
-