| 7c7fd88 | Robert Haas | 28 March 2011, 13:42:09 UTC | Mark up release notes using <link>. Unlike <xref>, this actually works. | 28 March 2011, 13:42:09 UTC |
| e5948e3 | Alvaro Herrera | 26 March 2011, 03:09:17 UTC | Add missing #include | 28 March 2011, 13:37:29 UTC |
| a720c28 | Tom Lane | 28 March 2011, 13:34:56 UTC | Get rid of links that don't work when building HISTORY. | 28 March 2011, 13:34:56 UTC |
| 20a1159 | Robert Haas | 28 March 2011, 01:35:15 UTC | Typo fix in SSI docs. Kevin Grittner | 28 March 2011, 01:35:15 UTC |
| de32982 | Robert Haas | 28 March 2011, 01:28:15 UTC | Correct "characters" to "bytes" in createdb docs. Susanne Ebrecht | 28 March 2011, 01:28:15 UTC |
| 7b66e2c | Greg Stark | 27 March 2011, 20:31:41 UTC | fix up a couple non-prototypes of the form foo() to be foo(void) -- found using -Wstrict-prototypes | 27 March 2011, 20:31:41 UTC |
| d0dd5c7 | Tom Lane | 27 March 2011, 17:29:52 UTC | Fix check_exclusion_constraint() to insert correct collations in ScanKeys. | 27 March 2011, 17:29:52 UTC |
| 87f2ad1 | Tom Lane | 27 March 2011, 16:51:04 UTC | Fix plpgsql to release SPI plans when a function or DO block is freed. This fixes the gripe I made a few months ago about DO blocks getting slower with repeated use. At least, it fixes it for the case where the DO block isn't aborted by an error. We could try running plpgsql_free_function_memory() even during error exit, but that seems a bit scary since it makes a lot of presumptions about the data structures being in good shape. It's probably reasonable to assume that repeated failures of DO blocks isn't a performance-critical case. | 27 March 2011, 16:51:04 UTC |
| de592e2 | Robert Haas | 27 March 2011, 01:18:53 UTC | Remove disclaimer stating that fsync=off slows down sync rep. The underlying problem that caused this phenomenon was fixed by commit 92f4786fa9b730fd12cbfe973eb96addc6e98924. | 27 March 2011, 01:19:06 UTC |
| ab1ef8e | Robert Haas | 27 March 2011, 01:11:15 UTC | Update release notes for latest commits. In addition, correct the entry for pg_object_description, and some other minor cleanup. | 27 March 2011, 01:13:55 UTC |
| 7208fae | Tom Lane | 26 March 2011, 22:28:40 UTC | Clean up cruft around collation initialization for tupdescs and scankeys. I found actual bugs in GiST and plpgsql; the rest of this is cosmetic but meant to decrease the odds of future bugs of omission. | 26 March 2011, 22:28:40 UTC |
| 0c9d9e8 | Tom Lane | 26 March 2011, 20:35:25 UTC | More collations cleanup, from trawling for missed collation assignments. Mostly cosmetic, though I did find that generateClonedIndexStmt failed to clone the index's collations. | 26 March 2011, 20:35:25 UTC |
| b23c9fa | Tom Lane | 26 March 2011, 18:25:48 UTC | Clean up a few failures to set collation fields in expression nodes. I'm not sure these have any non-cosmetic implications, but I'm not sure they don't, either. In particular, ensure the CaseTestExpr generated by transformAssignmentIndirection to represent the base target column carries the correct collation, because parse_collate.c won't fix that. Tweak lsyscache.c API so that we can get the appropriate collation without an extra syscache lookup. | 26 March 2011, 18:25:48 UTC |
| 92f4786 | Simon Riggs | 26 March 2011, 10:09:37 UTC | Additional test for each commit in sync rep path to plug minute possibility of race condition that would effect performance only. Requested by Robert Haas. Re-arrange related comments. | 26 March 2011, 10:09:37 UTC |
| bfa4440 | Tom Lane | 26 March 2011, 00:10:42 UTC | Pass collation to makeConst() instead of looking it up internally. In nearly all cases, the caller already knows the correct collation, and in a number of places, the value the caller has handy is more correct than the default for the type would be. (In particular, this patch makes it significantly less likely that eval_const_expressions will result in changing the exposed collation of an expression.) So an internal lookup is both expensive and wrong. | 26 March 2011, 00:10:42 UTC |
| c8e9935 | Tom Lane | 25 March 2011, 22:44:47 UTC | Fix failure to propagate collation in negate_clause(). Turns out it was this, and not so much plpgsql, that was at fault in Stefan Huehner's collation-error-in-a-trigger bug report of a couple weeks ago. | 25 March 2011, 22:44:47 UTC |
| 9b19c12 | Tom Lane | 25 March 2011, 22:21:25 UTC | Document collation handling in SQL and plpgsql functions. This is pretty minimal but covers the bare facts. | 25 March 2011, 22:21:25 UTC |
| a4425e3 | Tom Lane | 25 March 2011, 19:06:36 UTC | Fix collation handling in plpgsql functions. Make plpgsql treat the input collation as a polymorphism variable, so that we cache separate plans for each input collation that's used in a particular session, as per recent discussion. Propagate the input collation to all collatable input parameters. I chose to also propagate the input collation to all declared variables of collatable types, which is a bit more debatable but seems to be necessary for non-astonishing behavior. (Copying a parameter into a separate local variable shouldn't result in a change of behavior, for example.) There is enough infrastructure here to support declaring a collation for each local variable to override that default, but I thought we should wait to see what the field demand is before adding such a feature. In passing, remove exec_get_rec_fieldtype(), which wasn't used anywhere. Documentation patch to follow. | 25 March 2011, 19:06:36 UTC |
| f6f0916 | Robert Haas | 25 March 2011, 15:52:11 UTC | Remove alpha release notes. Temporarily move some of the alpha release note disclaimers into the regular release notes, for the sake of alpha5. | 25 March 2011, 15:52:11 UTC |
| 30f6136 | Robert Haas | 25 March 2011, 15:23:39 UTC | Make walreceiver send a reply after receiving data but before flushing it. It originally worked this way, but was changed by commit a8a8a3e0965201df88bdfdff08f50e5c06c552b7, since which time it's been impossible for walreceiver to ever send a reply with write_location and flush_location set to different values. | 25 March 2011, 15:28:16 UTC |
| 01dd34d | Alvaro Herrera | 25 March 2011, 15:20:14 UTC | Fix broken markup, and remove tabs | 25 March 2011, 15:21:12 UTC |
| 71ac48f | Michael Meskes | 24 March 2011, 21:18:11 UTC | Documented some ecpg command line options that were missing: -r no_indicator -r prepare -r questionsmarks | 25 March 2011, 01:30:50 UTC |
| 27dc7e2 | Tom Lane | 25 March 2011, 00:30:14 UTC | Fix handling of collation in SQL-language functions. Ensure that parameter symbols receive collation from the function's resolved input collation, and fix inlining to behave properly. BTW, this commit lays about 90% of the infrastructure needed to support use of argument names in SQL functions. Parsing of parameters is now done via the parser-hook infrastructure ... we'd just need to supply a column-ref hook ... | 25 March 2011, 00:30:23 UTC |
| a432e27 | Robert Haas | 24 March 2011, 22:44:49 UTC | Add post-creation hook for extensions, consistent with other object types. KaiGai Kohei | 24 March 2011, 22:44:49 UTC |
| 7b630e7 | Robert Haas | 24 March 2011, 20:57:12 UTC | Edits to 9.1 release notes. Add some new items and some additional details to existing items, mostly by cribbing from the 9.1alpha notes. Some additional clarifications and corrections elsewhere, and a few typo fixes. | 24 March 2011, 20:58:01 UTC |
| 3bba9ce | Tom Lane | 24 March 2011, 19:29:52 UTC | Clean up handling of COLLATE clauses in index column definitions. Ensure that COLLATE at the top level of an index expression is treated the same as a grammatically separate COLLATE. Fix bogus reverse-parsing logic in pg_get_indexdef. | 24 March 2011, 19:29:52 UTC |
| 472671e | Tom Lane | 23 March 2011, 20:56:55 UTC | Improve user-defined-aggregates documentation. On closer inspection, that two-element initcond value seems to have been a little white lie to avoid explaining the full behavior of float8_accum. But if people are going to expect the examples to be exactly correct, I suppose we'd better explain. Per comment from Thom Brown. | 23 March 2011, 20:56:55 UTC |
| b5f2f2a | Simon Riggs | 23 March 2011, 19:35:53 UTC | Minor changes to recovery pause behaviour. Change location LOG message so it works each time we pause, not just for final pause. Ensure that we pause only if we are in Hot Standby and can connect to allow us to run resume function. This change supercedes the code to override parameter recoveryPauseAtTarget to false if not attempting to enter Hot Standby, which is now removed. | 23 March 2011, 19:35:53 UTC |
| ba7d020 | Tom Lane | 23 March 2011, 16:33:14 UTC | Fix ancient typo in user-defined-aggregates documentation. The description of the initcond value for the built-in avg(float8) aggregate has been wrong since it was written. Noted by Disc Magnet. | 23 March 2011, 16:33:14 UTC |
| 19584ec | Robert Haas | 23 March 2011, 15:44:27 UTC | Remove synchronous_replication/max_wal_senders cross-check. This is no longer necessary, and might result in a situation where the configuration file is reloaded (and everything seems OK) but a subsequent restart of the database fails. Per an observation from Fujii Masao. | 23 March 2011, 15:44:27 UTC |
| b98ac46 | Simon Riggs | 23 March 2011, 13:30:05 UTC | Prevent intermittent hang in recovery from bgwriter interaction. Startup process waited for cleanup lock but when hot_standby = off the pid was not registered, so that the bgwriter would not wake the waiting process as intended. | 23 March 2011, 13:30:05 UTC |
| 856a230 | Peter Eisentraut | 22 March 2011, 15:44:38 UTC | Cosmetic capitalization fix | 23 March 2011, 01:59:53 UTC |
| ec497a5 | Simon Riggs | 22 March 2011, 23:10:35 UTC | Make FKs valid at creation when added as column constraints. Bug report from Alvaro Herrera | 22 March 2011, 23:10:35 UTC |
| 5d1d679 | Tom Lane | 22 March 2011, 21:20:50 UTC | Make initdb ignore locales for client-only encodings. While putting such entries into pg_collation is harmless (since backends will ignore entries that don't match the database encoding), it's also useless. | 22 March 2011, 21:20:50 UTC |
| 6e197cb | Tom Lane | 22 March 2011, 20:55:32 UTC | Improve reporting of run-time-detected indeterminate-collation errors. pg_newlocale_from_collation does not have enough context to give an error message that's even a little bit useful, so move the responsibility for complaining up to its callers. Also, reword ERRCODE_INDETERMINATE_COLLATION error messages in a less jargony, more message-style-guide-compliant fashion. | 22 March 2011, 20:55:32 UTC |
| 37d6d07 | Tom Lane | 22 March 2011, 19:58:03 UTC | Throw error for indeterminate collation of an ORDER/GROUP/DISTINCT target. This restores a parse error that was thrown (though only in the ORDER BY case) by the original collation patch. I had removed it in my recent revisions because it was thrown at a place where collations now haven't been computed yet; but I thought of another way to handle it. Throwing the error at parse time, rather than leaving it to be done at runtime, is good because a syntax error pointer is helpful for localizing the problem. We can reasonably assume that the comparison function for a collatable datatype will complain if it doesn't have a collation to use. Now the planner might choose to implement GROUP or DISTINCT via hashing, in which case no runtime error would actually occur, but it seems better to throw error consistently rather than let the error depend on what the planner chooses to do. Another possible objection is that the user might specify a nondefault sort operator that doesn't care about collation ... but that's surely an uncommon usage, and it wouldn't hurt him to throw in a COLLATE clause anyway. This change also makes the ORDER BY/GROUP BY/DISTINCT case more consistent with the UNION/INTERSECT/EXCEPT case, which was already coded to throw this error even though the same objections could be raised there. | 22 March 2011, 19:58:03 UTC |
| 1192ba8 | Tom Lane | 22 March 2011, 17:00:24 UTC | Avoid potential deadlock in InitCatCachePhase2(). Opening a catcache's index could require reading from that cache's own catalog, which of course would acquire AccessShareLock on the catalog. So the original coding here risks locking index before heap, which could deadlock against another backend trying to get exclusive locks in the normal order. Because InitCatCachePhase2 is only called when a backend has to start up without a relcache init file, the deadlock was seldom seen in the field. (And by the same token, there's no need to worry about any performance disadvantage; so not much point in trying to distinguish exactly which catalogs have the risk.) Bug report, diagnosis, and patch by Nikhil Sontakke. Additional commentary by me. Back-patch to all supported branches. | 22 March 2011, 17:00:48 UTC |
| 6e8e7cc | Simon Riggs | 22 March 2011, 16:23:54 UTC | Update docs to say you need fsync to make sync rep work fast. | 22 March 2011, 16:23:54 UTC |
| 8df08c8 | Tom Lane | 22 March 2011, 04:34:31 UTC | Reimplement planner's handling of MIN/MAX aggregate optimization (again). 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. | 22 March 2011, 04:34:31 UTC |
| 6d8096e | Heikki Linnakangas | 21 March 2011, 09:25:25 UTC | When two base backups are started at the same time with pg_basebackup, 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. | 21 March 2011, 09:25:25 UTC |
| 62bf9c2 | Bruce Momjian | 21 March 2011, 03:17:21 UTC | Markup and wording improvements for 9.1 release notes. | 21 March 2011, 03:17:21 UTC |
| 78fce29 | Bruce Momjian | 20 March 2011, 23:36:44 UTC | Another 9.1 release note typo fix. | 20 March 2011, 23:36:44 UTC |
| e8f4c24 | Bruce Momjian | 20 March 2011, 23:35:19 UTC | Fix snapshot isolation level typo in 9.1 release notes. | 20 March 2011, 23:35:19 UTC |
| f670c19 | Bruce Momjian | 20 March 2011, 21:43:04 UTC | Reorder some 9.1 release item documentation entries, fix some awkward wording. | 20 March 2011, 21:43:04 UTC |
| 9b095fb | Tom Lane | 20 March 2011, 18:35:39 UTC | Add some platform-independent tests for the collation feature. 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. | 20 March 2011, 18:35:39 UTC |
| 82e4d45 | Tom Lane | 20 March 2011, 17:34:31 UTC | Suppress platform-dependent unused-variable warning. 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. | 20 March 2011, 17:34:31 UTC |
| 176d5ba | Tom Lane | 20 March 2011, 16:43:39 UTC | Fix up handling of C/POSIX collations. 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 March 2011, 16:44:13 UTC |
| c2f4ea4 | Bruce Momjian | 20 March 2011, 13:33:37 UTC | Move PITR and StreamingRep up one level of heading in the 9.1 release notes. Remove excessive linking to pg_ctl manual page. Reorder incompatibility sections. | 20 March 2011, 13:33:37 UTC |
| 0f96ae6 | Magnus Hagander | 20 March 2011, 12:28:05 UTC | Misc minor fixes to 9.1 release notes Thom Brown | 20 March 2011, 12:28:05 UTC |
| 08607c9 | Bruce Momjian | 20 March 2011, 04:27:23 UTC | Word-wrap 9.1 release note lines. | 20 March 2011, 04:27:23 UTC |
| b2c5b3d | Bruce Momjian | 20 March 2011, 03:58:53 UTC | Add links to documentation from 9.1 release notes. | 20 March 2011, 03:59:33 UTC |
| b310b6e | Tom Lane | 20 March 2011, 00:29:08 UTC | Revise collation derivation method and expression-tree representation. 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. | 20 March 2011, 00:30:08 UTC |
| 025f4c7 | Bruce Momjian | 19 March 2011, 21:21:49 UTC | Add SGML markup for keywords, terms, functions, commands, etc. | 19 March 2011, 21:21:49 UTC |
| b03b17c | Bruce Momjian | 19 March 2011, 20:39:17 UTC | Initial version of PG 9.1 release notes. | 19 March 2011, 20:39:47 UTC |
| 6f9192d | Magnus Hagander | 19 March 2011, 17:44:35 UTC | Rename ident authentication over local connections to peer 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 March 2011, 17:44:35 UTC |
| 4a00148 | Magnus Hagander | 19 March 2011, 15:38:50 UTC | Properly clear the verbose output of pg_basebackup Don't leave partial filename information on the last status or dangling characters if the previous filename was longer than the current one. | 19 March 2011, 15:38:50 UTC |
| 56bb7f2 | Bruce Momjian | 19 March 2011, 14:04:34 UTC | Remove "all balls" mention of network address; change IPv6 address to ::/0. | 19 March 2011, 14:05:04 UTC |
| fbcf4b9 | Robert Haas | 19 March 2011, 02:09:57 UTC | Fix possible "tuple concurrently updated" error in ALTER TABLE. 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. | 19 March 2011, 02:09:57 UTC |
| 7275899 | Robert Haas | 19 March 2011, 01:43:45 UTC | Move synchronous_standbys_defined updates from WAL writer to BG writer. 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. | 19 March 2011, 01:43:45 UTC |
| f78ba0a | Robert Haas | 19 March 2011, 01:22:43 UTC | Woops. Previous patch to remove -X options missed getopt_long calls(). Noted by Tom Lane. | 19 March 2011, 01:23:28 UTC |
| 0191e12 | Bruce Momjian | 18 March 2011, 23:18:08 UTC | Document that the timestamp returned by pg_last_xact_replay_timestamp is the time on the primary that the transaction was generated. | 18 March 2011, 23:18:08 UTC |
| a7136b7 | Bruce Momjian | 18 March 2011, 22:41:02 UTC | Document the all-balls IPv6 address. | 18 March 2011, 22:41:33 UTC |
| 7a37900 | Robert Haas | 18 March 2011, 14:20:22 UTC | Make synchronous replication query cancel/die messages more consistent. Per a gripe from Thom Brown about my previous commit in this area, commit 9a56dc3389b9470031e9ef8e45c95a680982e01a. | 18 March 2011, 14:20:22 UTC |
| c5eb835 | Robert Haas | 18 March 2011, 13:44:44 UTC | Remove ancient -X options to pg_dump, pg_dumpall, pg_restore. 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. | 18 March 2011, 13:44:44 UTC |
| 777e8c0 | Robert Haas | 18 March 2011, 12:09:09 UTC | Remove bogus semicolons in recoveryPausesHere. Without this, the startup process goes into a tight loop, consuming 100% of one CPU and failing to respond to interrupts. | 18 March 2011, 12:09:09 UTC |
| f94c6f9 | Robert Haas | 17 March 2011, 19:46:44 UTC | Minor fixes for high availability documentation. Erik Rijkers and me | 17 March 2011, 19:46:44 UTC |
| 76dbb46 | Robert Haas | 17 March 2011, 19:10:55 UTC | Protocol documentation for Hot Standby feedback messages. | 17 March 2011, 19:10:55 UTC |
| 02b1f84 | Robert Haas | 17 March 2011, 18:43:14 UTC | Remove bogus comment. | 17 March 2011, 18:43:57 UTC |
| 1c249fc | Alvaro Herrera | 17 March 2011, 15:28:46 UTC | Fix PL/Python memory leak involving array slices Report and patch from Daniel Popowich, bug #5842 (with some debugging help from Alex Hunsaker) | 17 March 2011, 18:26:15 UTC |
| 8c0a5eb | Peter Eisentraut | 17 March 2011, 18:19:51 UTC | Raise maximum value of several timeout parameters 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. | 17 March 2011, 18:19:51 UTC |
| 84abea7 | Robert Haas | 17 March 2011, 18:02:41 UTC | Add pause_at_recovery_target to recovery.conf.sample; improve docs. Fujii Masao, but with the proposed behavior change reverted, and the rest adjusted accordingly. | 17 March 2011, 18:04:11 UTC |
| 9a56dc3 | Robert Haas | 17 March 2011, 17:10:42 UTC | Fix various possible problems with synchronous replication. 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 March 2011, 17:12:21 UTC |
| e148443 | Bruce Momjian | 17 March 2011, 04:26:03 UTC | Document guc context values, and reference them from the config doc section. Tom Lane | 17 March 2011, 04:27:01 UTC |
| 5b079cb | Andrew Dunstan | 17 March 2011, 04:06:52 UTC | Use correct PATH separator for Cygwin in pg_regress.c. 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. | 17 March 2011, 04:06:52 UTC |
| ad3aff4 | Robert Haas | 16 March 2011, 21:46:15 UTC | Tab completion for \pset format and \pset linestyle. Pavel Stehule | 16 March 2011, 21:46:15 UTC |
| 5f588e2 | Robert Haas | 16 March 2011, 12:11:24 UTC | Corrections to CREATE FOREIGN TABLE documentation. Omit incorrect = sign, and properly document server_name parameter. Shigeru Hanada | 16 March 2011, 12:13:02 UTC |
| 72cfc17 | Tom Lane | 16 March 2011, 01:51:36 UTC | Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT. 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. | 16 March 2011, 01:52:10 UTC |
| 898a14e | Bruce Momjian | 16 March 2011, 00:52:35 UTC | Remove unused copy_dir() function from pg_upgrade. | 16 March 2011, 00:52:35 UTC |
| a858ca1 | Bruce Momjian | 16 March 2011, 00:47:31 UTC | Adjust doc wording about the casting exceptions for composite types. | 16 March 2011, 00:47:31 UTC |
| 2b8364d | Bruce Momjian | 16 March 2011, 00:18:35 UTC | Add hint suggesting the use of EXECUTE CREATE TABLE ... AS for EXECUTE INTO. | 16 March 2011, 00:18:35 UTC |
| b774efa | Bruce Momjian | 15 March 2011, 23:50:02 UTC | Fix spelling error in fuzzystrmatch docs. | 15 March 2011, 23:50:02 UTC |
| df4a959 | Bruce Momjian | 15 March 2011, 16:43:39 UTC | Wording adjustment for restart_after_crash entry Specifically, mention that "restart" is disabled by this parameter. | 15 March 2011, 16:43:39 UTC |
| ddd6ff2 | Bruce Momjian | 15 March 2011, 15:26:20 UTC | Add database comments to template0 and postgres databases, and improve the comments on the template1 database. No catalog version bump because they are just comments. | 15 March 2011, 15:26:57 UTC |
| f0f3617 | Robert Haas | 15 March 2011, 15:25:04 UTC | Minor sync rep documentation improvements. - 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. | 15 March 2011, 15:25:04 UTC |
| 5ca4dfc | Robert Haas | 15 March 2011, 14:22:58 UTC | Remove 13 keywords that are used only for ROLE options. Review by Tom Lane. | 15 March 2011, 14:22:58 UTC |
| 01c1a12 | Magnus Hagander | 14 March 2011, 18:46:52 UTC | Remove special case allowing parameters to ident auth for initdb 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. | 14 March 2011, 18:51:09 UTC |
| f12423d | Tom Lane | 14 March 2011, 16:52:03 UTC | Adjust regression test to avoid platform-dependent failure. 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 March 2011, 16:52:31 UTC |
| b051a34 | Bruce Momjian | 14 March 2011, 14:40:14 UTC | Remove duplicate time-based macros recently added. | 14 March 2011, 14:40:14 UTC |
| a2eb9e0 | Tom Lane | 13 March 2011, 16:57:14 UTC | Simplify list traversal logic in add_path(). Its mechanism for recovering after deleting the current list cell was a bit klugy. Borrow the technique used in other places. | 13 March 2011, 16:57:14 UTC |
| 696d1f7 | Tom Lane | 12 March 2011, 21:30:36 UTC | Make all comparisons done for/with statistics use the default collation. 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 March 2011, 21:30:36 UTC |
| 94fe9c0 | Bruce Momjian | 12 March 2011, 14:38:56 UTC | Use "backend process" rather than "backend server", where appropriate. | 12 March 2011, 14:38:56 UTC |
| 3a3f39f | Bruce Momjian | 12 March 2011, 14:31:18 UTC | Use macros for time-based constants, rather than constants. | 12 March 2011, 14:35:56 UTC |
| 3d9f7ec | Peter Eisentraut | 12 March 2011, 08:07:23 UTC | Add test case for collation mismatch in recursive query This isn't very important by itself, but was left on my list of things without test coverage for the collation feature. | 12 March 2011, 08:07:23 UTC |
| 2a26639 | Tom Lane | 12 March 2011, 00:04:02 UTC | On further reflection, we'd better do the same in int.c. 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. | 12 March 2011, 00:04:02 UTC |
| 7233099 | Tom Lane | 11 March 2011, 23:18:55 UTC | Put in some more safeguards against executing a division-by-zero. 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 | 11 March 2011, 23:18:55 UTC |
| 8acdb8b | Tom Lane | 11 March 2011, 21:27:51 UTC | Split CollateClause into separate raw and analyzed node types. CollateClause is now used only in raw grammar output, and CollateExpr after parse analysis. This is for clarity and to avoid carrying collation names in post-analysis parse trees: that's both wasteful and possibly misleading, since the collation's name could be changed while the parsetree still exists. Also, clean up assorted infelicities and omissions in processing of the node type. | 11 March 2011, 21:28:18 UTC |
| 7a8f439 | Bruce Momjian | 11 March 2011, 19:33:10 UTC | In docs, rename "backwards compatibility" to "backward compatibility" for consistency. | 11 March 2011, 19:33:10 UTC |
| e3c732a | Tom Lane | 11 March 2011, 18:20:11 UTC | Create an explicit concept of collations that work for any encoding. Use collencoding = -1 to represent such a collation in pg_collation. We need this to make the "default" entry work sanely, and a later patch will fix the C/POSIX entries to be represented this way instead of duplicating them across all encodings. All lookup operations now search first for an entry that's database-encoding-specific, and then for the same name with collencoding = -1. Also some incidental code cleanup in collationcmds.c and pg_collation.c. | 11 March 2011, 18:20:11 UTC |
| ac435a7 | Tom Lane | 11 March 2011, 16:41:14 UTC | Remove duplicate indexterm to silence openjade wrning. | 11 March 2011, 16:41:51 UTC |
| 4869d10 | Bruce Momjian | 11 March 2011, 16:36:42 UTC | Update documentation on FreeBSD write cache control. | 11 March 2011, 16:36:42 UTC |
