| ce8a3e6 | Tom Lane | 20 April 2007, 03:27:34 UTC | Fix markup. Security: CVE-2007-2138 | 20 April 2007, 03:27:34 UTC |
| e05d987 | PostgreSQL Daemon | 20 April 2007, 03:20:42 UTC | Update configure.in version number Security: tag for release | 20 April 2007, 03:20:42 UTC |
| d694bdd | Tom Lane | 20 April 2007, 02:37:49 UTC | Support explicit placement of the temporary-table schema within search_path. This is needed to allow a security-definer function to set a truly secure value of search_path. Without it, a malicious user can use temporary objects to execute code with the privileges of the security-definer function. Even pushing the temp schema to the back of the search path is not quite good enough, because a function or operator at the back of the path might still capture control from one nearer the front due to having a more exact datatype match. Hence, disable searching the temp schema altogether for functions and operators. Security: CVE-2007-2138 | 20 April 2007, 02:37:49 UTC |
| 4e6c6a4 | Tom Lane | 19 April 2007, 22:44:38 UTC | Sync timezone data with 2007e zic release. | 19 April 2007, 22:44:38 UTC |
| c0a5622 | Tom Lane | 19 April 2007, 22:23:31 UTC | Fix missed PACKAGE_STRING. | 19 April 2007, 22:23:31 UTC |
| 7fc2507 | Tom Lane | 19 April 2007, 20:24:10 UTC | Repair PANIC condition in hash indexes when a previous index extension attempt failed (due to lock conflicts or out-of-space). We might have already extended the index's filesystem EOF before failing, causing the EOF to be beyond what the metapage says is the last used page. Hence the invariant maintained by the code needs to be "EOF is at or beyond last used page", not "EOF is exactly the last used page". Problem was created by my patch of 2006-11-19 that attempted to repair bug #2737. Since that was back-patched to 7.4, this needs to be as well. Per report and test case from Vlastimil Krejcir. | 19 April 2007, 20:24:10 UTC |
| 266a0ff | Tom Lane | 19 April 2007, 16:33:32 UTC | Fix plpgsql to avoid reference to already-freed memory when returning a pass-by-reference data type and the RETURN statement is within an EXCEPTION block. Bug introduced by my fix of 2007-01-28 to use per-subtransaction ExprContexts/EStates; since that wasn't back-patched into older branches, only 8.2 and HEAD are affected. Per report from Gary Winslow. | 19 April 2007, 16:33:32 UTC |
| 9de4b61 | Bruce Momjian | 19 April 2007, 13:03:07 UTC | Release wording updates for releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19. | 19 April 2007, 13:03:07 UTC |
| 90e4b46 | Bruce Momjian | 19 April 2007, 03:07:32 UTC | Stamp releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19. | 19 April 2007, 03:07:32 UTC |
| fe48792 | Bruce Momjian | 19 April 2007, 02:47:52 UTC | Release note updates for 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19. | 19 April 2007, 02:47:52 UTC |
| d3753aa | Peter Eisentraut | 18 April 2007, 20:01:39 UTC | Translation updates | 18 April 2007, 20:01:39 UTC |
| 65c531d | Bruce Momjian | 18 April 2007, 02:29:39 UTC | Update docs/error message for CSV quote/escape --- must be ASCII. Backpatch doc change to 8.2.X. | 18 April 2007, 02:29:39 UTC |
| 4e93443 | Bruce Momjian | 18 April 2007, 00:18:31 UTC | Document that the COPY delimiter must be an ASCII byte, rather than a multi-byte value. It can also be a single-byte encoded character if the client and server versions match. Backpatch to 8.2.X. | 18 April 2007, 00:18:31 UTC |
| 2edda80 | Tom Lane | 17 April 2007, 20:03:10 UTC | Rewrite choose_bitmap_and() to make it more robust in the presence of competing alternatives for indexes to use in a bitmap scan. The former coding took estimated selectivity as an overriding factor, causing it to sometimes choose indexes that were much slower to scan than ones with a slightly worse selectivity. It was also too narrow-minded about which combinations of indexes to consider ANDing. The rewrite makes it pay more attention to index scan cost than selectivity; this seems sane since it's impossible to have very bad selectivity with low cost, whereas the reverse isn't true. Also, we now consider each index alone, as well as adding each index to an AND-group led by each prior index, for a total of about O(N^2) rather than O(N) combinations considered. This makes the results much less dependent on the exact order in which the indexes are considered. It's still a lot cheaper than an O(2^N) exhaustive search. A prefilter step eliminates all but the cheapest of those indexes using the same set of WHERE conditions, to keep the effective value of N down in scenarios where the DBA has created lots of partially-redundant indexes. | 17 April 2007, 20:03:10 UTC |
| ff663c9 | Magnus Hagander | 16 April 2007, 20:16:11 UTC | Don't write timing output in quiet mode. Merlin Moncure | 16 April 2007, 20:16:11 UTC |
| aeb5417 | Tom Lane | 16 April 2007, 18:42:17 UTC | Fix pg_dump to not crash if -t or a similar switch is used to select a serial sequence for dumping without also selecting its owning table. Make it not try to emit ALTER SEQUENCE OWNED BY in this situation. Per report from Michael Nolan. | 16 April 2007, 18:42:17 UTC |
| 366e9ee | Tom Lane | 12 April 2007, 17:11:00 UTC | Rearrange mdsync() looping logic to avoid the problem that a sufficiently fast flow of new fsync requests can prevent mdsync() from ever completing. This was an unforeseen consequence of a patch added in Mar 2006 to prevent the fsync request queue from overflowing. Problem identified by Heikki Linnakangas and independently by ITAGAKI Takahiro; fix based on ideas from Takahiro-san, Heikki, and Tom. Back-patch as far as 8.1 because a previous back-patch introduced the problem into 8.1 ... | 12 April 2007, 17:11:00 UTC |
| 707964b | Tom Lane | 12 April 2007, 15:04:41 UTC | Cancel pending fsync requests during WAL replay of DROP DATABASE, per bug report from David Darville. Back-patch as far as 8.1, which may or may not have the problem but it seems a safe change anyway. | 12 April 2007, 15:04:41 UTC |
| 627939c | Bruce Momjian | 07 April 2007, 15:43:47 UTC | Backpatch doc change SYMETRIC -> SYMMETRIC, for 8.2.X. | 07 April 2007, 15:43:47 UTC |
| 3ac7d76 | Tom Lane | 02 April 2007, 18:49:36 UTC | Fix check_sql_fn_retval to allow the case where a SQL function declared to return void ends with a SELECT, if that SELECT has a single result that is also of type void. Without this, it's hard to write a void function that calls another void function. Per gripe from Peter. Back-patch as far as 8.0. | 02 April 2007, 18:49:36 UTC |
| 100beb0 | Teodor Sigaev | 02 April 2007, 11:42:25 UTC | Fix caching of unsuccessful initialization of parser or configuration. Per report from Listmail <lists@peufeu.com> | 02 April 2007, 11:42:25 UTC |
| 4dd2d91 | Bruce Momjian | 30 March 2007, 03:19:19 UTC | Update SSL description for when SSL root.crt/server.crt is required; add link to libpq SSL does from server docs. Backpatch to 8.2.X. | 30 March 2007, 03:19:19 UTC |
| 0e95abd | Tom Lane | 30 March 2007, 00:13:05 UTC | Fix oversight in coding of _bt_start_vacuum: we can't assume that the LWLock will be released by transaction abort before _bt_end_vacuum gets called. If either of these "can't happen" errors actually happened, we'd freeze up trying to acquire an already-held lock. Latest word is that this does not explain Martin Pitt's trouble report, but it still looks like a bug. | 30 March 2007, 00:13:05 UTC |
| 2dd336b | Tom Lane | 27 March 2007, 03:25:35 UTC | Fix typo, ensable -> enable, per Steve Gieseking. | 27 March 2007, 03:25:35 UTC |
| a467a7a | Tom Lane | 26 March 2007, 17:23:45 UTC | Fix seriously broken markup for libpq-envars cross-references. | 26 March 2007, 17:23:45 UTC |
| 07fe241 | Tatsuo Ishii | 26 March 2007, 11:35:42 UTC | Fix pg_wchar_table's maxmblen field of EUC_CN, EUC_TW, MULE_INTERNAL and GB18030. patches from ITAGAKI Takahiro. | 26 March 2007, 11:35:42 UTC |
| 720a9cc | Bruce Momjian | 24 March 2007, 21:46:25 UTC | Document that LDAP URLs should be double-quoted in pg_hba.conf because commas are often present in the URL. Backpatch to 8.2.X. | 24 March 2007, 21:46:25 UTC |
| 1e0cba9 | Tom Lane | 24 March 2007, 16:46:28 UTC | Fix broken markup. | 24 March 2007, 16:46:28 UTC |
| fc565cf | Teodor Sigaev | 22 March 2007, 15:59:09 UTC | Fix parser bug on Windows with UTF8 encoding and C locale, the reason was sizeof(wchar_t) = 2 instead of 4. | 22 March 2007, 15:59:09 UTC |
| 60e67c1 | Tom Lane | 19 March 2007, 16:30:40 UTC | Fix 8.2 breakage of domains over array types, and add a regression test case to cover it. Per report from Anton Pikhteryev. | 19 March 2007, 16:30:40 UTC |
| 32311df | Tom Lane | 17 March 2007, 03:15:47 UTC | SPI_cursor_open failed to enforce that only read-only queries could be executed in read_only mode. This could lead to various relatively-subtle failures, such as an allegedly stable function returning non-stable results. Bug goes all the way back to the introduction of read-only mode in 8.0. Per report from Gaetano Mendola. | 17 March 2007, 03:15:47 UTC |
| 009dac8 | Alvaro Herrera | 16 March 2007, 15:06:46 UTC | Fix uninitialized value in pgstatindex leading to invalid values being reported in some cases. Report and patch from Tatsuhito Kasahara. Also fix a couple of other bugs I noticed in skimming the surrounding code. | 16 March 2007, 15:06:46 UTC |
| aef05db | Tom Lane | 14 March 2007, 18:49:04 UTC | Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). The fix is to recheck HeapTupleSatisfiesVacuum while following a chain forward, and to stop if a DEAD tuple is reached. Each contiguous group of RECENTLY_DEAD tuples will therefore be copied as a separate chain. The patch also adds a couple of extra sanity checks to verify correct behavior. Per report and test case from Pavan Deolasee. | 14 March 2007, 18:49:04 UTC |
| 1a72f35 | Tom Lane | 14 March 2007, 17:38:15 UTC | Arrange to install a "posixrules" entry in our timezone database, so that POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. We could consider changing localtime.c's TZDEFRULESTRING, but since that facility can only deal with one DST transition rule, it seems fairly useless now; might as well just plan to override it using a "posixrules" entry. Backpatch as far as 8.0. There isn't much we can do in 7.x ... either your libc gets it right, or it doesn't. | 14 March 2007, 17:38:15 UTC |
| 8a7b386 | Alvaro Herrera | 11 March 2007, 06:44:11 UTC | Fix a race condition that caused pg_database_size() and pg_tablespace_size() to fail if an object was removed between calls to ReadDir() and stat(). Per discussion in pgsql-hackers. http://archives.postgresql.org/pgsql-hackers/2007-03/msg00671.php Bug report and patch by Michael Fuhr. | 11 March 2007, 06:44:11 UTC |
| 5ea7b17 | Magnus Hagander | 08 March 2007, 19:27:48 UTC | Remove unsafe calling of WSAStartup and WSACleanup from DllMain. Move the inline cleanup call around so it will be called in the right order, and be called on errors. Per report from Tokuharu Yuzawa. | 08 March 2007, 19:27:48 UTC |
| 8e010ac | Tom Lane | 08 March 2007, 17:03:43 UTC | Fix vac_update_relstats to ensure it always sends a relcache inval message, even if none of the fields in the pg_class row change. This behavior is necessary to ensure other backends flush rd_targblock values that might point to truncated-away pages. We got this right pre-8.2 but it was broken by overoptimistic change to not write out the pg_class row if unchanged. Per report from Pavan Deolasee. | 08 March 2007, 17:03:43 UTC |
| 2b1abc8 | Teodor Sigaev | 07 March 2007, 21:25:18 UTC | Athough cube is a varlena type, nowhere was a detoasting of cube's value, so fix it. Add macroses DatumGetNDBOX, PG_GETARG_NDBOX and PG_RETURN_NDBOX. Backpatch for 8.2 too. Previous versions use version 0 calling conventions. And fmgr code detoast values for user-defined functions. | 07 March 2007, 21:25:18 UTC |
| cafbf1e | Tom Lane | 06 March 2007, 22:45:23 UTC | Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Along the way, fix an omission in eval_const_expressions_mutator: it failed to copy the relabelformat field when processing a RelabelType. No known observable failures from this, but it definitely isn't intended behavior. | 06 March 2007, 22:45:23 UTC |
| 3530283 | Tom Lane | 01 March 2007, 20:07:02 UTC | Fix miscalculation of stats collector's write delay, introduced in revision 1.117. | 01 March 2007, 20:07:02 UTC |
| 4408902 | Tom Lane | 01 March 2007, 18:50:36 UTC | Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. | 01 March 2007, 18:50:36 UTC |
| bde73ab | Michael Meskes | 27 February 2007, 13:27:13 UTC | Backported bug fix for #2956. | 27 February 2007, 13:27:13 UTC |
| 9395aa5 | Bruce Momjian | 21 February 2007, 16:42:43 UTC | Update Chinese FAQs to have two versions, a traditional Chinese version (Taiwan) and a Simplified version (China (PRC)). Backpatch to 8.2.X. Daojing.Zhou | 21 February 2007, 16:42:43 UTC |
| 664009e | Bruce Momjian | 20 February 2007, 19:59:18 UTC | Update "encode" documentation to mention that 'escape' only changes null bytes and backslashes, remove "ASCII" mention. Backpatch to 8.2.X. | 20 February 2007, 19:59:18 UTC |
| 6f90273 | Bruce Momjian | 20 February 2007, 18:47:34 UTC | Update information_schema documentation to match system tables. Backpatch to 8.2.X. | 20 February 2007, 18:47:34 UTC |
| 57bcfe0 | Bruce Momjian | 20 February 2007, 18:11:17 UTC | More clearly document that most PostgreSQL utilities support libpq environment variables. Backpatch to 8.2.X. | 20 February 2007, 18:11:17 UTC |
| 44764fb | Bruce Momjian | 20 February 2007, 14:54:51 UTC | Spell check on array patch. | 20 February 2007, 14:54:51 UTC |
| 0586e9b | Bruce Momjian | 20 February 2007, 14:34:29 UTC | Update array slice documentation to be clearer. | 20 February 2007, 14:34:29 UTC |
| 7194ab3 | Bruce Momjian | 20 February 2007, 14:05:02 UTC | Comment-out documentation for IS OF because it doesn't conform to the ISO SQL behavior. Backpatch removal to 8.2.X. | 20 February 2007, 14:05:02 UTC |
| d9341ce | Bruce Momjian | 20 February 2007, 00:25:16 UTC | Document IS [NOT] OF, which was added in 7.3. | 20 February 2007, 00:25:16 UTC |
| c2039e4 | Bruce Momjian | 19 February 2007, 22:06:30 UTC | Update PQfree() documentation to be clearer, backpatch to 8.2.X. | 19 February 2007, 22:06:30 UTC |
| 7c2e6f3 | Magnus Hagander | 19 February 2007, 15:05:21 UTC | Fix pg_dump on win32 to properly dump files larger than 2Gb when using binary dump formats. | 19 February 2007, 15:05:21 UTC |
| 812a929 | Tom Lane | 18 February 2007, 19:49:30 UTC | Fix portal management code to support non-default command completion tags for portals using PORTAL_UTIL_SELECT strategy. This is currently significant only for FETCH queries, which are supposed to include a count in the tag. Seems it's been broken since 7.4, but nobody noticed before Knut Lehre. | 18 February 2007, 19:49:30 UTC |
| 33b4159 | Tom Lane | 16 February 2007, 20:57:26 UTC | Adjust the definition of is_pushed_down so that it's always true for INNER JOIN quals, just like WHERE quals, even if they reference every one of the join's relations. Now that we can reorder outer and inner joins, it's possible for such a qual to end up being assigned to an outer join plan node, and we mustn't have it treated as a join qual rather than a filter qual for the node. (If it were, the join could produce null-extended rows that it shouldn't.) Per bug report from Pelle Johansson. | 16 February 2007, 20:57:26 UTC |
| 36e24e8 | Tom Lane | 16 February 2007, 03:49:10 UTC | Fix another problem in 8.2 changes that allowed "one-time" qual conditions to be checked at plan levels below the top; namely, we have to allow for Result nodes inserted just above a nestloop inner indexscan. Should think about using the general Param mechanism to pass down outer-relation variables, but for the moment we need a back-patchable solution. Per report from Phil Frost. | 16 February 2007, 03:49:10 UTC |
| 84222cf | Tom Lane | 16 February 2007, 00:14:08 UTC | Restructure code that is responsible for ensuring that clauseless joins are considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them. | 16 February 2007, 00:14:08 UTC |
| 9e850cf | Tom Lane | 15 February 2007, 03:07:21 UTC | Repair oversight in 8.2 change that improved the handling of "pseudoconstant" WHERE clauses. createplan.c is now willing to stick a gating Result node almost anywhere in the plan tree, and in particular one can wind up directly underneath a MergeJoin node. This means it had better be willing to handle Mark/Restore. Fortunately, that's trivial in such cases, since we can just pass off the call to the input node (which the planner has previously ensured can handle Mark/Restore). Per report from Phil Frost. | 15 February 2007, 03:07:21 UTC |
| 538a983 | Tom Lane | 13 February 2007, 19:39:48 UTC | Disallow committing a prepared transaction unless we are in the same database it was executed in. Someday it might be nice to allow cross-DB commits, but work would be needed in NOTIFY and perhaps other places. Per Heikki. | 13 February 2007, 19:39:48 UTC |
| bc16005 | Tom Lane | 13 February 2007, 02:31:12 UTC | Repair bug in 8.2's new logic for planning outer joins: we have to allow joins that overlap an outer join's min_righthand but aren't fully contained in it, to support joining within the RHS after having performed an outer join that can commute with this one. Aside from the direct fix in make_join_rel(), fix has_join_restriction() and GEQO's desirable_join() to consider this possibility. Per report from Ian Harding. | 13 February 2007, 02:31:12 UTC |
| 15f910d | Teodor Sigaev | 12 February 2007, 14:15:13 UTC | Fix backend crash in parsing incorrect tsquery. Per report from Jon Rosebaugh <jon@inklesspen.com> | 12 February 2007, 14:15:13 UTC |
| 9c6cfdc | Magnus Hagander | 11 February 2007, 15:12:21 UTC | Fix for early log messages during postmaster startup getting lost when running as a service on Win32. Per report from Harald Armin Massa. Backpatch to 8.2. | 11 February 2007, 15:12:21 UTC |
| d6c1e16 | Bruce Momjian | 08 February 2007, 20:33:54 UTC | Fix bug when localized to_char() day or month names were incorectly trnasformed to lower or upper string. Backpatch to 8.2.X. Pavel Stehule | 08 February 2007, 20:33:54 UTC |
| d1be38c | Tom Lane | 08 February 2007, 18:37:43 UTC | Fix an ancient logic error in plpgsql's exec_stmt_block: it thought it could get away with not (re)initializing a local variable if the variable is marked "isconst" and not "isnull". Unfortunately it makes this decision after having already freed the old value, meaning that something like for i in 1..10 loop declare c constant text := 'hi there'; leads to subsequent accesses to freed memory, and hence probably crashes. (In particular, this is why Asif Ali Rehman's bug leads to crash and not just an unexpectedly-NULL value for SQLERRM: SQLERRM is marked CONSTANT and so triggers this error.) The whole thing seems wrong on its face anyway: CONSTANT means that you can't change the variable inside the block, not that the initializer expression is guaranteed not to change value across successive block entries. Hence, remove the "optimization" instead of trying to fix it. | 08 February 2007, 18:37:43 UTC |
| 799290b | Tom Lane | 08 February 2007, 18:37:38 UTC | Rearrange use of plpgsql_add_initdatums() so that only the parsing of a DECLARE section needs to know about it. Formerly, everyplace besides DECLARE that created variables needed to do "plpgsql_add_initdatums(NULL)" to prevent those variables from being sucked up as part of a subsequent DECLARE block. This is obviously error-prone, and in fact the SQLSTATE/SQLERRM patch had failed to do it for those two variables, leading to the bug recently exhibited by Asif Ali Rehman: a DECLARE within an exception handler tried to reinitialize SQLERRM. Although the SQLSTATE/SQLERRM patch isn't in any pre-8.1 branches, and so I can't point to a demonstrable failure there, it seems wise to back-patch this into the older branches anyway, just to keep the logic similar to HEAD. | 08 February 2007, 18:37:38 UTC |
| 760f482 | Bruce Momjian | 08 February 2007, 17:04:48 UTC | This patch fixes shared_preload_libraries on Windows hosts. It forces each backend to re-load all shared_preload_libraries. Backpatch to 8.2.X. Korry Douglas | 08 February 2007, 17:04:48 UTC |
| e1c2664 | Bruce Momjian | 08 February 2007, 04:31:41 UTC | Update URL for "Generalized Partial Indexes" paper to point to a cached version. Backpatch to 8.2.X. | 08 February 2007, 04:31:41 UTC |
| 76f46f5 | Bruce Momjian | 08 February 2007, 03:57:52 UTC | Document that wal_sync_method open_* methods use O_DIRECT, if available. Backpatch to 8.2.X. | 08 February 2007, 03:57:52 UTC |
| d015e14 | Bruce Momjian | 07 February 2007, 04:23:01 UTC | Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. | 07 February 2007, 04:23:01 UTC |
| 18b0d7d | Tom Lane | 07 February 2007, 03:59:30 UTC | Fix PG_VERSION_NUM too. | 07 February 2007, 03:59:30 UTC |
| 98e08d1 | Bruce Momjian | 07 February 2007, 03:48:58 UTC | Stamp releases 8.2.3, 8.1.8, 8.0.12. No release notes yet. | 07 February 2007, 03:48:58 UTC |
| 0b36bbf | Bruce Momjian | 07 February 2007, 03:16:59 UTC | Update FAQ for 8.2.3. | 07 February 2007, 03:16:59 UTC |
| 04dc48b | Tom Lane | 06 February 2007, 22:49:30 UTC | Fix an error in the original coding of holdable cursors: PersistHoldablePortal thought that it didn't have to reposition the underlying tuplestore if the portal is atEnd. But this is not so, because tuplestores have separate read and write cursors ... and the read cursor hasn't moved from the start. This mistake explains bug #2970 from William Zhang. Note: the coding here is pretty inefficient, but given that no one has noticed this bug until now, I'd say hardly anyone uses the case where the cursor has been advanced before being persisted. So maybe it's not worth worrying about. | 06 February 2007, 22:49:30 UTC |
| b93d4a7 | Bruce Momjian | 06 February 2007, 18:38:04 UTC | Backpatch FAQs to 8.2.X branch. | 06 February 2007, 18:38:04 UTC |
| 8d24b8b | Tom Lane | 06 February 2007, 17:35:27 UTC | Remove typmod checking from the recent security-related patches. It turns out that ExecEvalVar and friends don't necessarily have access to a tuple descriptor with correct typmod: it definitely can contain -1, and possibly might contain other values that are different from the Var's value. Arguably this should be cleaned up someday, but it's not a simple change, and in any case typmod discrepancies don't pose a security hazard. Per reports from numerous people :-( I'm not entirely sure whether the failure can occur in 8.0 --- the simple test cases reported so far don't trigger it there. But back-patch the change all the way anyway. | 06 February 2007, 17:35:27 UTC |
| 33623b5 | Michael Meskes | 06 February 2007, 10:48:28 UTC | Backported regression test changes from HEAD so the buildfarm hopefully gets green again. | 06 February 2007, 10:48:28 UTC |
| b8dd3a8 | Michael Meskes | 06 February 2007, 09:41:44 UTC | Backported va_list handling cleanup | 06 February 2007, 09:41:44 UTC |
| a95abdf | Tom Lane | 06 February 2007, 06:50:33 UTC | Fix a performance regression in 8.2: optimization of MIN/MAX into indexscans had stopped working for tables buried inside views or sub-selects. This is because I had gotten rid of the simplify_jointree() preprocessing step, and optimize_minmax_aggregates() wasn't smart enough to deal with a non-canonical FromExpr. Per gripe from Bill Howe. | 06 February 2007, 06:50:33 UTC |
| 5338847 | Tom Lane | 06 February 2007, 03:05:00 UTC | Not only did we agree that this 'hint' doesn't belong here, but the markup's broken. So just remove it... | 06 February 2007, 03:05:00 UTC |
| de9acc9 | Bruce Momjian | 05 February 2007, 22:18:18 UTC | Trim down environment variable instructions for Win32, backpatch to 8.2.X. | 05 February 2007, 22:18:18 UTC |
| e7c63e5 | Andrew Dunstan | 05 February 2007, 15:23:24 UTC | Pass modern COPY syntax to backend, since copy (query) does not accept old syntax. Per complaint from Michael Fuhr. | 05 February 2007, 15:23:24 UTC |
| 54111e9 | Tom Lane | 04 February 2007, 20:00:49 UTC | Don't MAXALIGN in the checks to decide whether a tuple is over TOAST's threshold for tuple length. On 4-byte-MAXALIGN machines, the toast code creates tuples that have t_len exactly TOAST_TUPLE_THRESHOLD ... but this number is not itself maxaligned, so if heap_insert maxaligns t_len before comparing to TOAST_TUPLE_THRESHOLD, it'll uselessly recurse back to tuptoaster.c, wasting cycles. (It turns out that this does not happen on 8-byte-MAXALIGN machines, because for them the outer MAXALIGN in the TOAST_MAX_CHUNK_SIZE macro reduces TOAST_MAX_CHUNK_SIZE so that toast tuples will be less than TOAST_TUPLE_THRESHOLD in size. That MAXALIGN is really incorrect, but we can't remove it now, see below.) There isn't any particular value in maxaligning before comparing to the thresholds, so just don't do that, which saves a small number of cycles in itself. These numbers should be rejiggered to minimize wasted space on toast-relation pages, but we can't do that in the back branches because changing TOAST_MAX_CHUNK_SIZE would force an initdb (by changing the contents of toast tables). We can move the toast decision thresholds a bit, though, which is what this patch effectively does. Thanks to Pavan Deolasee for discovering the unintended recursion. Back-patch into 8.2, but not further, pending more testing. (HEAD is about to get a further patch modifying the thresholds, so it won't help much for testing this form of the patch.) | 04 February 2007, 20:00:49 UTC |
| e5352a2 | Bruce Momjian | 04 February 2007, 04:00:33 UTC | Update wording. | 04 February 2007, 04:00:33 UTC |
| 1015fd5 | Bruce Momjian | 04 February 2007, 03:58:58 UTC | Add documentation for Windows on how to set an environment variable. Backpatch to 8.2.X. | 04 February 2007, 03:58:58 UTC |
| d68f1ec | Bruce Momjian | 03 February 2007, 23:01:13 UTC | Document that a client-only install using: gmake -C src/bin install does install a few server-only binaries. | 03 February 2007, 23:01:13 UTC |
| 554d3a6 | Bruce Momjian | 03 February 2007, 02:47:35 UTC | Fix configure detection code when --with-ldap and --enable-thread-safety are both used. Backpatch to 8.2.X. Albe Laurenz | 03 February 2007, 02:47:35 UTC |
| 3714d82 | Neil Conway | 02 February 2007, 16:10:10 UTC | Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under Windows. Per Magnus Hagander, this is not recommended. | 02 February 2007, 16:10:10 UTC |
| d06a16c | Tom Lane | 02 February 2007, 00:14:22 UTC | Stamp release 8.2.2. Security: CVE-2007-0555, CVE-2007-0556 | 02 February 2007, 00:14:22 UTC |
| 40cf433 | Tom Lane | 02 February 2007, 00:10:33 UTC | Update release notes for security-related releases in all active branches. Security: CVE-2007-0555, CVE-2007-0556 | 02 February 2007, 00:10:33 UTC |
| 23326cd | Tom Lane | 02 February 2007, 00:07:28 UTC | Repair failure to check that a table is still compatible with a previously made query plan. Use of ALTER COLUMN TYPE creates a hazard for cached query plans: they could contain Vars that claim a column has a different type than it now has. Fix this by checking during plan startup that Vars at relation scan level match the current relation tuple descriptor. Since at that point we already have at least AccessShareLock, we can be sure the column type will not change underneath us later in the query. However, since a backend's locks do not conflict against itself, there is still a hole for an attacker to exploit: he could try to execute ALTER COLUMN TYPE while a query is in progress in the current backend. Seal that hole by rejecting ALTER TABLE whenever the target relation is already open in the current backend. This is a significant security hole: not only can one trivially crash the backend, but with appropriate misuse of pass-by-reference datatypes it is possible to read out arbitrary locations in the server process's memory, which could allow retrieving database content the user should not be able to see. Our thanks to Jeff Trout for the initial report. Security: CVE-2007-0556 | 02 February 2007, 00:07:28 UTC |
| 78e039c | Tom Lane | 02 February 2007, 00:03:17 UTC | Repair insufficiently careful type checking for SQL-language functions: we should check that the function code returns the claimed result datatype every time we parse the function for execution. Formerly, for simple scalar result types we assumed the creation-time check was sufficient, but this fails if the function selects from a table that's been redefined since then, and even more obviously fails if check_function_bodies had been OFF. This is a significant security hole: not only can one trivially crash the backend, but with appropriate misuse of pass-by-reference datatypes it is possible to read out arbitrary locations in the server process's memory, which could allow retrieving database content the user should not be able to see. Our thanks to Jeff Trout for the initial report. Security: CVE-2007-0555 | 02 February 2007, 00:03:17 UTC |
| 14a866b | Bruce Momjian | 01 February 2007, 21:03:00 UTC | Mention file system replication as a high availability solution in the shared hardware section, and mention DRBD as a popular solution. | 01 February 2007, 21:03:00 UTC |
| b7c9821 | Tom Lane | 01 February 2007, 19:23:00 UTC | Fix plpgsql so that when a local variable has no initial-value expression, an error will be thrown correctly if the variable is of a NOT NULL domain. Report and almost-correct fix from Sergiy Vyshnevetskiy (bug #2948). | 01 February 2007, 19:23:00 UTC |
| 3c7d9ad | Neil Conway | 01 February 2007, 19:18:14 UTC | Backpatch last night's fix for broken markup to the 8.2 branch. | 01 February 2007, 19:18:14 UTC |
| e3b12f7 | Bruce Momjian | 01 February 2007, 05:12:46 UTC | Add 8.2.0 "Incomatibilities" documentation that pg_dump's -n and -t behavior has changed. | 01 February 2007, 05:12:46 UTC |
| da45866 | Bruce Momjian | 01 February 2007, 04:56:41 UTC | Backpatch FAQs to stable branch. | 01 February 2007, 04:56:41 UTC |
| 1762c43 | Peter Eisentraut | 31 January 2007, 08:33:34 UTC | Translation updates | 31 January 2007, 08:33:34 UTC |
| 8c14912 | Bruce Momjian | 31 January 2007, 04:13:28 UTC | Document need for periodic REINDEX in VACUUM FULL cases. | 31 January 2007, 04:13:28 UTC |
| e2d6898 | Bruce Momjian | 30 January 2007, 22:29:40 UTC | Update documentation for backslashes to mention escape string syntax more, and standard_conforming_strings less, because in the future non-E strings will not treat backslashes specially. Also use E'' strings where backslashes are used in examples. (The existing examples would have drawn warnings.) Backpatch to 8.2.X. | 30 January 2007, 22:29:40 UTC |
| 08c17d6 | Tom Lane | 30 January 2007, 22:05:20 UTC | Repair oversights in the mechanism used to store compiled plpgsql functions. The original coding failed (tried to access deallocated memory) if there were two active call sites (fn_extra pointers) for the same function and the function definition was updated. Also, if an update of a recursive function was detected upon nested entry to the function, the existing compiled version was summarily deallocated, resulting in crash upon return to the outer instance. Problem observed while studying a bug report from Sergiy Vyshnevetskiy. Bug does not exist before 8.1 since older versions just leaked the memory of obsoleted compiled functions, rather than trying to reclaim it. | 30 January 2007, 22:05:20 UTC |
| 971230d | Tom Lane | 30 January 2007, 18:02:28 UTC | Add SPI_push/SPI_pop calls so that datatype input and output functions called by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Somewhat arbitrarily, I've chosen to back-patch this as far as 8.0. Given the lack of prior complaints, it doesn't seem critical for 7.x. | 30 January 2007, 18:02:28 UTC |
