| 817a894 | Tom Lane | 06 May 2013, 20:57:06 UTC | Stamp 9.3beta1. | 06 May 2013, 20:57:06 UTC |
| f1ff90c | Tom Lane | 06 May 2013, 20:02:37 UTC | Desultory copy-editing of the 9.3 release notes. I had time for a quick review of the notes, so here are some fixes. | 06 May 2013, 20:02:37 UTC |
| 1d6c72a | Tom Lane | 06 May 2013, 17:26:51 UTC | Move materialized views' is-populated status into their pg_class entries. Previously this state was represented by whether the view's disk file had zero or nonzero size, which is problematic for numerous reasons, since it's breaking a fundamental assumption about heap storage. This was done to allow unlogged matviews to revert to unpopulated status after a crash despite our lack of any ability to update catalog entries post-crash. However, this poses enough risk of future problems that it seems better to not support unlogged matviews until we can find another way. Accordingly, revert that choice as well as a number of existing kluges forced by it in favor of creating a pg_class.relispopulated flag column. | 06 May 2013, 17:27:22 UTC |
| 5da5798 | Tom Lane | 06 May 2013, 16:28:13 UTC | Back out some recent translation updates. Very old versions of msgfmt choke on these specific messages, for reasons that are unclear at the moment. Remove them so that we can ship a beta release and not get complaints from testers (these messages will just go untranslated, instead, and we're hardly at 100% coverage anyway). Peter Eisentraut will look for a better fix later. | 06 May 2013, 16:28:13 UTC |
| 3223b25 | Tom Lane | 06 May 2013, 15:57:05 UTC | Disallow unlogged materialized views. The initial implementation of this feature was really unsupportable, because it's relying on the physical size of an on-disk file to carry the relation's populated/unpopulated state, which is at least a modularity violation and could have serious long-term consequences. We could say that an unlogged matview goes to empty on crash, but not everybody likes that definition, so let's just remove the feature for 9.3. We can add it back when we have a less klugy implementation. I left the grammar and tab-completion support for CREATE UNLOGGED MATERIALIZED VIEW in place, since it's harmless and allows delivering a more specific error message about the unsupported feature. I'm committing this separately to ease identification of what should be reverted when/if we are able to re-enable the feature. | 06 May 2013, 16:00:06 UTC |
| c298660 | Bruce Momjian | 06 May 2013, 14:57:23 UTC | 9.3 release notes: use "restoration" Andrew Dunstan | 06 May 2013, 14:57:23 UTC |
| 2fbffc0 | Bruce Momjian | 06 May 2013, 14:56:27 UTC | 9.3 release notes: Add cache of local locks Mention this also helps in the restoring of pg_dumps. Jeff Janes | 06 May 2013, 14:56:27 UTC |
| c750aa9 | Bruce Momjian | 06 May 2013, 14:47:10 UTC | 9.3 release notes: update from Amit Kapila No need to mention wal_receiver_status_interval. | 06 May 2013, 14:47:31 UTC |
| b2ad82d | Simon Riggs | 06 May 2013, 14:37:17 UTC | Execute SET TRANSACTION SNAPSHOT during pg_dump Previous coding set the SQL buffer but never executed Bug noted by me during beta testing | 06 May 2013, 14:37:17 UTC |
| 8b06e6a | Bruce Momjian | 06 May 2013, 12:59:39 UTC | Revert idea of zer-padding padding session id in log_line_prefix Removal of doc adjustment and release note mention as well. | 06 May 2013, 12:59:39 UTC |
| 539ecc9 | Peter Eisentraut | 06 May 2013, 02:34:23 UTC | Translation updates | 06 May 2013, 02:34:23 UTC |
| 626e6ed | Tom Lane | 04 May 2013, 20:41:22 UTC | Improve behavior of \watch with non-tuple-returning commands. Print the command tag if we get PGRES_COMMAND_OK, and throw an error for other cases. Per gripe from Michael Paquier. In passing, add an fflush(), just to be real sure the output appears before we sleep. | 04 May 2013, 20:41:22 UTC |
| 083d8fa | Bruce Momjian | 04 May 2013, 17:23:04 UTC | docs: Improve log_line_prefix session_id query | 04 May 2013, 17:23:04 UTC |
| f87f214 | Bruce Momjian | 04 May 2013, 17:15:54 UTC | docs: log_line_prefix session id fix Restore 4-byte designation for docs. Fix 9.3 doc query to properly pad to four digits. Backpatch to all active branches Per suggestions from Ian Lawrence Barwick | 04 May 2013, 17:15:54 UTC |
| 75d1406 | Bruce Momjian | 04 May 2013, 15:52:18 UTC | 9.3 docs: wording fixes From Erik Rijkers | 04 May 2013, 15:52:18 UTC |
| 262a362 | Bruce Momjian | 04 May 2013, 15:05:16 UTC | docs: fix log_line_prefix session id docs Backpatch to 9.2. Report from Ian Lawrence Barwick | 04 May 2013, 15:05:16 UTC |
| c008ca6 | Bruce Momjian | 04 May 2013, 14:44:49 UTC | 9.3 release notes: adjustments Fixes from Peter Geoghegan, Ian Lawrence Barwick, Marti Raudsepp | 04 May 2013, 14:44:49 UTC |
| 2497dc0 | Bruce Momjian | 04 May 2013, 01:11:35 UTC | 9.3 release notes: move compatibility items into their own section | 04 May 2013, 01:11:35 UTC |
| 1136d7a | Bruce Momjian | 04 May 2013, 00:55:03 UTC | 9.3 release notes: Add markup for pg_backup_start_time() | 04 May 2013, 00:55:03 UTC |
| 15f27ae | Bruce Momjian | 03 May 2013, 23:40:23 UTC | 9.3 release notes: Add links to SGML sections | 03 May 2013, 23:40:23 UTC |
| 14c7a74 | Bruce Momjian | 03 May 2013, 18:48:12 UTC | 9.3 release notes: add markup for text Still need to add links for new features. | 03 May 2013, 18:48:24 UTC |
| c091c43 | Tom Lane | 03 May 2013, 18:39:28 UTC | Improve SPI documentation about null-flags arrays. Clarify the description of nulls[] arguments, and use the same wording for all SPI functions with this type of argument. Per gripe from Yuriy Rusinov. | 03 May 2013, 18:39:28 UTC |
| 5fcf944 | Bruce Momjian | 03 May 2013, 17:30:58 UTC | 9.3 release notes: update for current commits Also, remove broken link in release.sgml. | 03 May 2013, 17:30:58 UTC |
| c8f61eb | Bruce Momjian | 02 May 2013, 23:14:20 UTC | 9.3 release notes: suggested improvements from Jeff Janes and Josh Berkus | 02 May 2013, 23:14:23 UTC |
| b69ec7c | Kevin Grittner | 02 May 2013, 22:33:03 UTC | Prevent (auto)vacuum from truncating first page of populated matview. Per report from Fujii Masao, with regression test using his example. | 02 May 2013, 22:33:03 UTC |
| 095018b | Bruce Momjian | 02 May 2013, 14:27:06 UTC | pg_test_fsync: update output to show usecs/op clearer | 02 May 2013, 14:27:12 UTC |
| 5f8b431 | Andrew Dunstan | 01 May 2013, 22:47:18 UTC | Use correct length to convert json unicode escapes. Bug reported on IRC - fix due to Andrew Gierth. | 01 May 2013, 22:47:18 UTC |
| 50c1374 | Tom Lane | 01 May 2013, 22:26:50 UTC | Fix permission tests for views/tables proven empty by constraint exclusion. A view defined as "select <something> where false" had the curious property that the system wouldn't check whether users had the privileges necessary to select from it. More generally, permissions checks could be skipped for tables referenced in sub-selects or views that were proven empty by constraint exclusion (although some quick testing suggests this seldom happens in cases of practical interest). This happened because the planner failed to include rangetable entries for such tables in the finished plan. This was noticed in connection with erroneous handling of materialized views, but actually the issue is quite unrelated to matviews. Therefore, revert commit 200ba1667b3a8d7a9d559d2f05f83d209c9d8267 in favor of a more direct test for the real problem. Back-patch to 9.2 where the bug was introduced (by commit 7741dd6590073719688891898e85f0cb73453159). | 01 May 2013, 22:26:50 UTC |
| 200ba16 | Kevin Grittner | 30 April 2013, 20:02:43 UTC | Add regression test for bug fixed by recent refactoring. Test case by Andres Freund for bug fixed by Tom Lane's refactoring in commit 5194024d72f33fb209e10f9ab0ada7cc67df45b7 | 30 April 2013, 20:02:43 UTC |
| 87d3b35 | Simon Riggs | 30 April 2013, 14:49:24 UTC | Fix pg_upgrade for 9.3 with data checksums. Previous changes misconstrued pg_upgrade internals causing build farm breakages. | 30 April 2013, 14:49:24 UTC |
| be475a2 | Simon Riggs | 30 April 2013, 14:32:10 UTC | Revert previous temporary patch | 30 April 2013, 14:32:10 UTC |
| 2837721 | Simon Riggs | 30 April 2013, 13:34:47 UTC | Temporarily silence pg_upgrade's checksums check | 30 April 2013, 13:34:47 UTC |
| ceabfb2 | Simon Riggs | 30 April 2013, 12:27:47 UTC | Bump PG_CONTROL_VERSION to 937 | 30 April 2013, 12:27:47 UTC |
| 4439517 | Simon Riggs | 30 April 2013, 11:27:12 UTC | Record data_checksum_version in control file. The value is not used anywhere in code, but will allow future changes to the checksum version should that become necessary in the future. | 30 April 2013, 11:27:12 UTC |
| 7309243 | Simon Riggs | 30 April 2013, 07:15:49 UTC | Ensure we MarkBufferDirty before visibilitymap_set() logs the heap page and sets the LSN. Otherwise a checkpoint could occur between those actions and leave us in an inconsistent state. Jeff Davis | 30 April 2013, 07:15:49 UTC |
| fdea253 | Simon Riggs | 30 April 2013, 05:59:26 UTC | Compiler optimizations for page checksum code. Ants Aasma and Jeff Davis | 30 April 2013, 05:59:26 UTC |
| 3d53173 | Peter Eisentraut | 30 April 2013, 02:17:29 UTC | pg_upgrade: Remove PGPORT handling from test suite This code was left over from when pg_upgrade paid attention to PGPORT. Now it would only affects the regression test run before the test run of pg_upgrade. You can still set PGPORT for that, but there is no reason to have the test driver default it to 50432. | 30 April 2013, 02:17:29 UTC |
| 187ca5e | Peter Eisentraut | 30 April 2013, 01:55:12 UTC | Revert "pg_ctl: Add idempotent option" This reverts commit 87306184580c9c49717b00d48a2f9e717f21e0a8. The behavior in certain cases is still being debated, and it's too late to solve this before beta. | 30 April 2013, 01:55:12 UTC |
| db9f0e1 | Tom Lane | 29 April 2013, 18:49:01 UTC | Postpone creation of pathkeys lists to fix bug #8049. This patch gets rid of the concept of, and infrastructure for, non-canonical PathKeys; we now only ever create canonical pathkey lists. The need for non-canonical pathkeys came from the desire to have grouping_planner initialize query_pathkeys and related pathkey lists before calling query_planner. However, since query_planner didn't actually *do* anything with those lists before they'd been made canonical, we can get rid of the whole mess by just not creating the lists at all until the point where we formerly canonicalized them. There are several ways in which we could implement that without making query_planner itself deal with grouping/sorting features (which are supposed to be the province of grouping_planner). I chose to add a callback function to query_planner's API; other alternatives would have required adding more fields to PlannerInfo, which while not bad in itself would create an ABI break for planner-related plugins in the 9.2 release series. This still breaks ABI for anything that calls query_planner directly, but it seems somewhat unlikely that there are any such plugins. I had originally conceived of this change as merely a step on the way to fixing bug #8049 from Teun Hoogendoorn; but it turns out that this fixes that bug all by itself, as per the added regression test. The reason is that now get_eclass_for_sort_expr is adding the ORDER BY expression at the end of EquivalenceClass creation not the start, and so anything that is in a multi-member EquivalenceClass has already been created with correct em_nullable_relids. I am suspicious that there are related scenarios in which we still need to teach get_eclass_for_sort_expr to compute correct nullable_relids, but am not eager to risk destabilizing either 9.2 or 9.3 to fix bugs that are only hypothetical. So for the moment, do this and stop here. Back-patch to 9.2 but not to earlier branches, since they don't exhibit this bug for lack of join-clause-movement logic that depends on em_nullable_relids being correct. (We might have to revisit that choice if any related bugs turn up.) In 9.2, don't change the signature of make_pathkeys_for_sortclauses nor remove canonicalize_pathkeys, so as not to risk more plugin breakage than we have to. | 29 April 2013, 18:50:03 UTC |
| 5fc8937 | Kevin Grittner | 29 April 2013, 18:05:26 UTC | Ensure ANALYZE phase is not skipped because of canceled truncate. Patch b19e4250b45e91c9cbdd18d35ea6391ab5961c8d attempted to preserve existing behavior regarding statistics generation in the case that a truncation attempt was canceled due to lock conflicts. It failed to do this accurately in two regards: (1) autovacuum had previously generated statistics if the truncate attempt failed to initially get the lock rather than having started the attempt, and (2) the VACUUM ANALYZE command had always generated statistics. Both of these changes were unintended, and are reverted by this patch. On review, there seems to be consensus that the previous failure to generate statistics when the truncate was terminated was more an unfortunate consequence of how that effort was previously terminated than a feature we want to keep; so this patch generates statistics even when an autovacuum truncation attempt terminates early. Another unintended change which is kept on the basis that it is an improvement is that when a VACUUM command is truncating, it will the new heuristic for avoiding blocking other processes, rather than keeping an AccessExclusiveLock on the table for however long the truncation takes. Per multiple reports, with some renaming per patch by Jeff Janes. Backpatch to 9.0, where problem was created. | 29 April 2013, 18:05:26 UTC |
| 91fa853 | Robert Haas | 29 April 2013, 10:29:32 UTC | Attempt to fix error recovery in COPY BOTH mode. Previously, libpq and the backend had opposite ideas about whether it was necessary for the client to send a CopyDone message after receiving an ErrorResponse, making it impossible to cleanly exit COPY BOTH mode. Fix libpq so that works correctly, adopting the backend's notion that an ErrorResponse kills the copy in both directions. Adjust receivelog.c to avoid a degradation in the quality of the resulting error messages. libpqwalreceiver.c is already doing the right thing, so no adjustment needed there. Add an explicit statement to the documentation explaining how this part of the protocol is supposed to work, in the hopes of avoiding future confusion in this area. Since the consequences of all this confusion are very limited, especially in the back-branches where no client ever attempts to exit COPY BOTH mode without closing the connection entirely, no back-patch. | 29 April 2013, 10:29:32 UTC |
| 43e7a66 | Simon Riggs | 29 April 2013, 08:05:27 UTC | Introduce new page checksum algorithm and module. Isolate checksum calculation to its own module, so that bufpage knows little if anything about the details of the calculation. This implementation is a modified FNV-1a hash checksum, details of which are given in the new checksum.c header comments. Basic implementation only, so we fix the output value. Later related commits will add version numbers to pg_control, compiler optimization flags and memory barriers. Ants Aasma, reviewed by Jeff Davis and Simon Riggs | 29 April 2013, 08:05:27 UTC |
| f8db76e | Tom Lane | 28 April 2013, 04:18:45 UTC | Editorialize a bit on new ProcessUtility() API. Choose a saner ordering of parameters (adding a new input param after the output params seemed a bit random), update the function's header comment to match reality (cmon folks, is this really that hard?), get rid of useless and sloppily-defined distinction between PROCESS_UTILITY_SUBCOMMAND and PROCESS_UTILITY_GENERATED. | 28 April 2013, 04:18:45 UTC |
| 5525e6c | Tom Lane | 28 April 2013, 03:11:28 UTC | Fix unsafe event-trigger coding in ProcessUtility(). We mustn't run any of the event-trigger support code when handling utility statements like START TRANSACTION or ABORT, because that code may need to refresh event-trigger cache data, which requires being inside a valid transaction. (This mistake explains the consistent build failures exhibited by the CLOBBER_CACHE_ALWAYS buildfarm members, as well as some irreproducible failures on other members.) The least messy fix seems to be to break standard_ProcessUtility into two functions, one that handles all the statements not supported by event triggers, and one that contains the event-trigger support code and handles the statements that are supported by event triggers. This change also fixes several inconsistencies, such as four cases where support had been installed for "ddl_event_start" but not "ddl_event_end" triggers, plus the fact that InvokeDDLCommandEventTriggersIfSupported() paid no mind to isCompleteQuery. Dimitri Fontaine and Tom Lane | 28 April 2013, 03:11:51 UTC |
| bbb4db4 | Peter Eisentraut | 28 April 2013, 03:06:37 UTC | pg_dump: Improve message formatting | 28 April 2013, 03:06:37 UTC |
| 5194024 | Tom Lane | 27 April 2013, 21:48:57 UTC | Incidental cleanup of matviews code. Move checking for unscannable matviews into ExecOpenScanRelation, which is a better place for it first because the open relation is already available (saving a relcache lookup cycle), and second because this eliminates the problem of telling the difference between rangetable entries that will or will not be scanned by the query. In particular we can get rid of the not-terribly-well-thought-out-or-implemented isResultRel field that the initial matviews patch added to RangeTblEntry. Also get rid of entirely unnecessary scannability check in the rewriter, and a bogus decision about whether RefreshMatViewStmt requires a parse-time snapshot. catversion bump due to removal of a RangeTblEntry field, which changes stored rules. | 27 April 2013, 21:48:57 UTC |
| f5d576c | Peter Eisentraut | 27 April 2013, 02:43:54 UTC | Improve message about failed transaction log archiving The old phrasing appeared to imply that the failure was terminal. Improve that by indicating that archiving will be tried again later. | 27 April 2013, 02:43:54 UTC |
| b53b603 | Peter Eisentraut | 27 April 2013, 02:13:03 UTC | Update config.guess and config.sub | 27 April 2013, 02:13:03 UTC |
| 41a2760 | Tom Lane | 26 April 2013, 19:48:24 UTC | Fix collation assignment for aggregates with ORDER BY. ORDER BY expressions were being treated the same as regular aggregate arguments for purposes of collation determination, but really they should not affect the aggregate's collation at all; only collations of the aggregate's regular arguments should affect it. In many cases this mistake would lead to incorrectly throwing a "collation conflict" error; but in some cases the corrected code will silently assign a different collation to the aggregate than before, for example agg(foo ORDER BY bar COLLATE "x") which will now use foo's collation rather than "x" for the aggregate. Given this risk and the lack of field complaints about the issue, it doesn't seem prudent to back-patch. In passing, rearrange code in assign_collations_walker so that we don't need multiple copies of the standard logic for computing collation of a node with children. (Previously, CaseExpr duplicated the standard logic, and we would have needed a third copy for Aggref without this change.) Andrew Gierth and David Fetter | 26 April 2013, 19:48:53 UTC |
| b42ea79 | Joe Conway | 26 April 2013, 18:50:00 UTC | Ensure that user created rows in extension tables get dumped if the table is explicitly requested, either with a -t/--table switch of the table itself, or by -n/--schema switch of the schema containing the extension table. Patch reviewed by Vibhor Kumar and Dimitri Fontaine. Backpatched to 9.1 when the extension management facility was added. | 26 April 2013, 19:02:40 UTC |
| 5eb7c4d | Robert Haas | 26 April 2013, 12:57:47 UTC | libpq: Fix a few bits that didn't get the memo about COPY BOTH. There's probably no real bug here at present, so not backpatching. But it seems good to make these bits consistent with the rest of libpq, so as to avoid future surprises. Patch by me. Review by Tom Lane. | 26 April 2013, 12:59:40 UTC |
| c3d09b3 | Tom Lane | 25 April 2013, 20:58:05 UTC | Avoid deadlock between concurrent CREATE INDEX CONCURRENTLY commands. There was a high probability of two or more concurrent C.I.C. commands deadlocking just before completion, because each would wait for the others to release their reference snapshots. Fix by releasing the snapshot before waiting for other snapshots to go away. Per report from Paul Hinze. Back-patch to all active branches. | 25 April 2013, 20:58:05 UTC |
| 447b317 | Heikki Linnakangas | 25 April 2013, 11:03:10 UTC | Fix typo in comment. Peter Geoghegan | 25 April 2013, 11:09:07 UTC |
| 6cf8462 | Peter Eisentraut | 25 April 2013, 02:51:10 UTC | pg_basebackup: Add missing newlines at end of lines | 25 April 2013, 02:51:10 UTC |
| 4c0343d | Peter Eisentraut | 25 April 2013, 02:50:33 UTC | initdb: Improve some messages | 25 April 2013, 02:50:33 UTC |
| 4d67961 | Peter Eisentraut | 24 April 2013, 02:46:36 UTC | PL/pgSQL doc: Add example for RETURN QUERY Erwin Brandstetter and Pavel Stěhule | 25 April 2013, 01:54:46 UTC |
| 0c1a160 | Heikki Linnakangas | 24 April 2013, 16:11:25 UTC | Add missing #include. On non-Windows systems, sys/time.h was pulled in by portability/instr_time.h, which pulled in time.h. We certainly should include time.h directly, since we're using time(2), but the indirect include masked the problem on most platforms. Andres Freund | 24 April 2013, 16:14:28 UTC |
| 63e2004 | Kevin Grittner | 24 April 2013, 13:39:06 UTC | Fix assertion failure for REFRESH MATERIALIZED VIEW in PL. This was due to incomplete implementation of rowcount reporting for RMV, which was due to initial waffling on whether it should be provided. It seems unlikely to be a useful or universally available number as more sophisticated techniques for maintaining matviews are added, so remove the partial support rather than completing it. Per report of Jeevan Chalke, but with a different fix | 24 April 2013, 13:39:06 UTC |
| 2317a63 | Simon Riggs | 24 April 2013, 11:21:18 UTC | Make fast promotion the default promotion mode. Continue to allow a request for synchronous checkpoints as a mechanism in case of problems. | 24 April 2013, 11:21:18 UTC |
| 173c252 | Bruce Momjian | 24 April 2013, 03:21:09 UTC | 9.3 release notes: adjustments per Alvaro | 24 April 2013, 03:21:09 UTC |
| 2d3edce | Bruce Momjian | 23 April 2013, 21:06:17 UTC | 9.3 release note updates from Dean Rasheed, Jov, Heikki Linnakangas, Erikjan Rijkers | 23 April 2013, 21:06:17 UTC |
| cc7b0c2 | Heikki Linnakangas | 23 April 2013, 10:48:14 UTC | Remove prototype for cube(text) function that doesn't exist anymore. Adrian Schreyer | 23 April 2013, 10:49:06 UTC |
| 98a1e7a | Bruce Momjian | 22 April 2013, 21:17:00 UTC | 9.3 release notes: add diacritics Alvaro Herrera | 22 April 2013, 21:17:00 UTC |
| e353884 | Bruce Momjian | 22 April 2013, 20:05:06 UTC | 9.3 release notes: adjustments per Alvaro and Robert | 22 April 2013, 20:05:10 UTC |
| ae73639 | Heikki Linnakangas | 22 April 2013, 18:51:14 UTC | Mention in docs that you can create SP-GiST indexes on range types. This is new in 9.3devel. | 22 April 2013, 18:51:14 UTC |
| 4f8799a | Bruce Momjian | 22 April 2013, 18:33:28 UTC | 9.3 release notes: apply fixes suggested by Alvaro | 22 April 2013, 18:33:28 UTC |
| beaa823 | Bruce Momjian | 22 April 2013, 14:22:43 UTC | 9.3 release notes: update streaming replication speedups Andres Freund | 22 April 2013, 14:22:49 UTC |
| e7d5ffe | Peter Eisentraut | 22 April 2013, 02:21:29 UTC | doc: Improve example formatting Erwin Brandstetter | 22 April 2013, 02:22:10 UTC |
| 53ecfdd | Peter Eisentraut | 22 April 2013, 02:16:12 UTC | doc: Fix syntax in example LANGUAGE 'plpgsql' no longer works. The single quotes need to be removed. Erwin Brandstetter | 22 April 2013, 02:22:10 UTC |
| c3ab4ea | Bruce Momjian | 22 April 2013, 01:05:31 UTC | In 9.3 release notes, split up items Split log shipping speed improvement and fail-over speed improvement items. Per request from Simon | 22 April 2013, 01:05:31 UTC |
| 4be535e | Bruce Momjian | 21 April 2013, 14:08:58 UTC | 9.3 release note adjustments per request from Andres Freund | 21 April 2013, 14:08:58 UTC |
| 1f2236e | Bruce Momjian | 21 April 2013, 13:16:23 UTC | Remove 9.3 item about fixing DROP INDEX CONCURRENTLY Already fixed in back branch. | 21 April 2013, 13:16:23 UTC |
| ac96e6a | Bruce Momjian | 21 April 2013, 13:14:34 UTC | 9.3 release note fixes Move commit_delay, fix Zoltan's name, and adjust range type histogram text. | 21 April 2013, 13:14:34 UTC |
| 864ec2f | Bruce Momjian | 21 April 2013, 13:05:16 UTC | Adjust 9.3 release notes per request from Simon | 21 April 2013, 13:05:16 UTC |
| ef3defc | Bruce Momjian | 21 April 2013, 04:57:18 UTC | Reorder 9.3 release note items Typo fix from David Fetter. | 21 April 2013, 04:57:18 UTC |
| f0922cb | Bruce Momjian | 20 April 2013, 21:31:06 UTC | More 9.3 release note reorderings | 20 April 2013, 21:31:06 UTC |
| 488eb90 | Bruce Momjian | 20 April 2013, 21:09:10 UTC | Fix Gilles Darold's name in 9.3 release notes. | 20 April 2013, 21:09:14 UTC |
| ac63dca | Tom Lane | 20 April 2013, 20:59:21 UTC | Fix longstanding race condition in plancache.c. When creating or manipulating a cached plan for a transaction control command (particularly ROLLBACK), we must not perform any catalog accesses, since we might be in an aborted transaction. However, plancache.c busily saved or examined the search_path for every cached plan. If we were unlucky enough to do this at a moment where the path's expansion into schema OIDs wasn't already cached, we'd do some catalog accesses; and with some more bad luck such as an ill-timed signal arrival, that could lead to crashes or Assert failures, as exhibited in bug #8095 from Nachiket Vaidya. Fortunately, there's no real need to consider the search path for such commands, so we can just skip the relevant steps when the subject statement is a TransactionStmt. This is somewhat related to bug #5269, though the failure happens during initial cached-plan creation rather than revalidation. This bug has been there since the plan cache was invented, so back-patch to all supported branches. | 20 April 2013, 21:00:23 UTC |
| 61b9623 | Bruce Momjian | 20 April 2013, 20:50:56 UTC | Reorder some 9.3 release item entries More to go. | 20 April 2013, 20:50:56 UTC |
| 22f956f | Bruce Momjian | 20 April 2013, 20:32:32 UTC | Push 9.3 release SGML file Forgotten in previous commit. | 20 April 2013, 20:32:32 UTC |
| e9a35c2 | Bruce Momjian | 20 April 2013, 20:29:58 UTC | Publish draft 9.3 release notes No links added yet. | 20 April 2013, 20:29:58 UTC |
| 540ec93 | Peter Eisentraut | 20 April 2013, 19:56:22 UTC | doc: Mention SATA alongside IDE for Linux suggested by Jov | 20 April 2013, 19:56:22 UTC |
| cc26ea9 | Peter Eisentraut | 20 April 2013, 15:04:41 UTC | Clean up references to SQL92 In most cases, these were just references to the SQL standard in general. In a few cases, a contrast was made between SQL92 and later standards -- those have been kept unchanged. | 20 April 2013, 15:04:41 UTC |
| 6e481eb | Tom Lane | 19 April 2013, 20:14:56 UTC | Improve error message when an FDW doesn't support WHERE CURRENT OF. If an FDW fails to take special measures with a CurrentOfExpr, we will end up trying to execute it as an ordinary qual, which was being treated as a purely internal failure condition. Provide a more user-oriented error message for such cases. | 19 April 2013, 20:14:56 UTC |
| 3353583 | Tom Lane | 19 April 2013, 17:28:45 UTC | Don't try to pass -I switch to postmaster in contrib/start-scripts/linux. Undo thinko in commit 87306184580c9c49717b00d48a2f9e717f21e0a8. Per bug #8098 from Catherine Devlin. | 19 April 2013, 17:28:45 UTC |
| 4580a4b | Robert Haas | 19 April 2013, 13:32:49 UTC | Fix typo in comment. Fabrízio de Royes Mello | 19 April 2013, 13:32:49 UTC |
| acd5803 | Peter Eisentraut | 19 April 2013, 03:35:19 UTC | Standardize spelling of "nonblocking" Only adjusted the user-exposed messages and documentation, not all source code comments. | 19 April 2013, 03:35:19 UTC |
| 5286963 | Bruce Momjian | 17 April 2013, 21:39:14 UTC | pg_upgrade: Add checksum C comment We might eventually allow checksum to no-checksum upgrades. | 17 April 2013, 21:39:19 UTC |
| f050457 | Robert Haas | 17 April 2013, 13:55:24 UTC | sepgsql: Minor improvement to test script, doc fix. KaiGai Kohei | 17 April 2013, 13:55:24 UTC |
| 0bf5c54 | Robert Haas | 17 April 2013, 13:52:25 UTC | sepgsql: One more getObjectIdentity in lieu of getObjectDescription. KaiGai Kohei, based on a suggestion from Álvaro Herrera | 17 April 2013, 13:52:59 UTC |
| b9bdaf3 | Peter Eisentraut | 17 April 2013, 01:42:10 UTC | doc: Update PQgetssl() documentation The return type of PQgetssl() was changed from SSL* to void* a long time ago, but the documentation was not updated. | 17 April 2013, 01:42:10 UTC |
| d61dddb | Bruce Momjian | 16 April 2013, 14:30:31 UTC | pgindent: add newline to die() so script line number is not reported on failure. | 16 April 2013, 14:30:35 UTC |
| 87ae9e7 | Heikki Linnakangas | 16 April 2013, 12:01:21 UTC | Remove some unused and seldom used fields from RelationAmInfo. This saves some memory from each index relcache entry. At least on a 64-bit machine, it saves just enough to shrink a typical relcache entry's memory usage from 2k to 1k. That's nice if you have a lot of backends and a lot of indexes. | 16 April 2013, 12:07:58 UTC |
| c74d586 | Peter Eisentraut | 16 April 2013, 02:33:24 UTC | Fix function return type confusion When parse_hba_line's return type was changed from bool to a pointer, the MANDATORY_AUTH_ARG macro wasn't adjusted. | 16 April 2013, 02:38:08 UTC |
| d788121 | Andrew Dunstan | 16 April 2013, 01:46:25 UTC | Mark json IO and extraction functions immutable. Per complaint from Hubert Depesz Lubaczewski. Catalog version bumped. | 16 April 2013, 01:46:25 UTC |
| 728ec97 | Andrew Dunstan | 15 April 2013, 20:20:21 UTC | Correct handling of NULL arguments in json funcs. Per gripe from Tom Lane. | 15 April 2013, 20:20:21 UTC |
| 410bed2 | Tom Lane | 15 April 2013, 16:49:29 UTC | Improve GiST index search performance for trigram regex queries. The initial coding just descended the index if any of the target trigrams were possibly present at the next level down. But actually we can apply trigramsMatchGraph() so as to take advantage of AND requirements when there are some. The input data might contain false positive matches, but that can only result in a false positive result, not false negative, so it's safe to do it this way. Alexander Korotkov | 15 April 2013, 16:49:29 UTC |
| e08fdf1 | Peter Eisentraut | 14 April 2013, 15:12:30 UTC | Add serial comma | 14 April 2013, 15:12:30 UTC |
| 8730618 | Peter Eisentraut | 14 April 2013, 03:42:42 UTC | pg_ctl: Add idempotent option This changes the behavior of the start and stop actions to exit successfully if the server was already started or stopped. This changes the default behavior of the start action: Before, if the server was already running, it would print a message and succeed. Now, that situation will result in an error. When running in idempotent mode, no message is printed and pg_ctl exits successfully. It was considered to just make the idempotent behavior the default and only option, but pg_upgrade needs the old behavior. | 14 April 2013, 03:42:42 UTC |
| ba66752 | Peter Eisentraut | 13 April 2013, 02:45:51 UTC | Fix sporadic rebuilds for .pc files The build of .pc (pkg-config) files depends on all makefiles in use, and in dependency tracking mode, the previous coding ended up including /dev/null as a makefile. Apparently, on some platforms the modification time of /dev/null changes sporadically, and so the .pc files would end up being rebuilt every so often. Fix that by changing the makefile code to do without using /dev/null. | 13 April 2013, 02:49:25 UTC |
