aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Ensure backwards compatibility for GetStableLatestTransactionId()Simon Riggs2012-05-12
|
* Fix obsolescent C declaration syntaxPeter Eisentraut2012-05-12
| | | | | gcc -Wextra/-Wold-style-declaration thinks that "inline" should go before the function return type.
* Explain compatibility item about language names a bit more.Tom Lane2012-05-11
| | | | | | | Since we've got an "open items" list item about this, apparently some people are pretty worried about it. In passing remove a lot of trailing whitespace.
* Update example of process titles shown by "ps".Tom Lane2012-05-11
| | | | | | This example was quite old: it lacked the WAL writer and autovac launcher as well as the more recently added checkpointer. Linux "ps" seems to show slightly different stuff now too.
* Cosmetic adjustments for postmaster's handling of checkpointer.Tom Lane2012-05-11
| | | | | Correct some comments, order some operations a bit more consistently. No functional changes.
* PL/Python: Adjust the regression tests for Python 3.3Peter Eisentraut2012-05-11
| | | | | | | | | The string representation of ImportError changed. Remove printing that; it's not necessary for the test. The order in which members of a dict are printed changed. But this was always implementation-dependent, so we have just been lucky for a long time. Do the printing the hard way to ensure sorted order.
* Fix contrib/citext's upgrade script to handle array and domain cases.Tom Lane2012-05-11
| | | | | | | | | | | | | | | | | | | | | | We previously recognized that citext wouldn't get marked as collatable during pg_upgrade from a pre-9.1 installation, and hacked its create-from-unpackaged script to manually perform the necessary catalog adjustments. However, we overlooked the fact that domains over citext, as well as the citext[] array type, need the same adjustments. Extend the script to handle those cases. Also, the documentation suggested that this was only an issue in pg_upgrade scenarios, which is quite wrong; loading any dump containing citext from a pre-9.1 server will also result in the type being wrongly marked. I approached the documentation problem by changing the 9.1.2 release note paragraphs about this issue, which is historically inaccurate. But it seems better than having the information scattered in multiple places, and leaving incorrect info in the 9.1.2 notes would be bad anyway. We'll still need to mention the issue again in the 9.1.4 notes, but perhaps they can just reference 9.1.2 for fix instructions. Per report from Evan Carroll. Back-patch into 9.1.
* Prevent loss of init fork when truncating an unlogged table.Robert Haas2012-05-11
| | | | Fixes bug #6635, reported by Akira Kurosawa.
* Remove extraneous #include "storage/proc.h"Simon Riggs2012-05-11
|
* Ensure age() returns a stable value rather than the latest valueSimon Riggs2012-05-11
|
* On GiST page split, release the locks on child pages before recursing up.Heikki Linnakangas2012-05-11
| | | | | | | | | | | | | | | | | | When inserting the downlinks for a split gist page, we used hold the locks on the child pages until the insertion into the parent - and recursively its parent if it had to be split too - were all completed. Change that so that the locks on child pages are released after the insertion in the immediate parent is done, before recursing further up the tree. This reduces the number of lwlocks that are held simultaneously. Holding many locks is bad for concurrency, and in extreme cases you can even hit the limit of 100 simultaneously held lwlocks in a backend. If you're really unlucky, you can hit the limit while in a critical section, which brings down the whole system. This fixes bug #6629 reported by Tom Forbes. Backpatch to 9.1. The page splitting code was rewritten in 9.1, and the old code did not have this problem.
* Improve discussion of setting server parameters.Tom Lane2012-05-10
| | | | | | | | Rewrite description of "include_if_exists" for clarity. Add subsection headings to make the structure of the page a little clearer. A couple other minor improvements too. Josh Kupershmidt and Tom Lane
* Revert catalog bump; was post-beta1, and unnecessary.Bruce Momjian2012-05-10
|
* Update comment for 'name' data type to say 63 "bytes".Bruce Momjian2012-05-10
| | | | Catalog version bump so everyone has the same comment for beta1.
* Stamp 9.2beta1.REL9_2_BETA1Tom Lane2012-05-10
|
* Tweak documentation wording to avoid "pdfendlink" failure.Tom Lane2012-05-10
| | | | | | HEAD documentation was failing to build as US PDF for me, because a link to "CREATE CAST" was getting split across pages. Adjust wording to remove this rather gratuitous cross-reference.
* Temporarily revert stats collector latch changes so we can ship beta1.Tom Lane2012-05-10
| | | | | | | | | This patch reverts commit 49340037ee3ab46cb24144a86705e35f272c24d5 and some follow-on tweaking in pgstat.c. While the basic scheme of latch-ifying the stats collector seems sound enough, it's failing on most Windows buildfarm members for unknown reasons, and there's no time left to debug that before 9.2beta1. Better to ship a beta version without this improvement. I hope to re-revert this once beta1 is out, though.
* Merge visibility map crash-safety into index-only scan release noteBruce Momjian2012-05-10
| | | | item, per Robert Haas.
* Make WaitLatch's WL_POSTMASTER_DEATH result trustworthy; simplify callers.Tom Lane2012-05-10
| | | | | | | | Per a suggestion from Peter Geoghegan, make WaitLatch responsible for verifying that the WL_POSTMASTER_DEATH bit it returns is truthful (by testing PostmasterIsAlive). Then simplify its callers, who no longer need to do that for themselves. Remove weasel wording about falsely-set result bits from WaitLatch's API contract.
* Properly capitalize the TimeZone parameterPeter Eisentraut2012-05-10
| | | | | | | For better or worse, it is implemented in mixed case, so document it as such, at least in the main listing, like DateStyle. Josh Kupershmidt
* Add comma after "Previously" as suggested by Josh KupershmidtBruce Momjian2012-05-10
|
* PL/Python: Fix slicing support for result objects for Python 3Peter Eisentraut2012-05-10
| | | | | | | | | | The old way of implementing slicing support by implementing PySequenceMethods.sq_slice no longer works in Python 3. You now have to implement PyMappingMethods.mp_subscript. Do this by simply proxying the call to the wrapped list of result dictionaries. Consolidate some of the subscripting regression tests. Jan Urbański
* PL/Python: Update incorrect commentPeter Eisentraut2012-05-10
| | | | Jan Urbański
* 9.2 release note updates from Peter GeogheganBruce Momjian2012-05-10
|
* Fix Windows implementation of PGSemaphoreLock.Tom Lane2012-05-10
| | | | | | | | | | | | | The original coding failed to reset ImmediateInterruptOK before returning, which would potentially allow a subsequent query-cancel interrupt to be accepted at an unsafe point. This is a really nasty bug since it's so hard to predict the consequences, but they could be unpleasant. Also, ensure that signal handlers are serviced before this function returns, even if the semaphore is already set. This should make the behavior more like Unix. Back-patch to all supported versions.
* Improve Windows implementation of WaitLatch/WaitLatchOrSocket.Tom Lane2012-05-10
| | | | | | | | | | Ensure that signal handlers are serviced before this function returns. This should make the behavior more like Unix. Also, add some more error checking, and make some other cosmetic improvements. No back-patch since it's not clear whether this is fixing any live bug that would affect 9.1. I'm more concerned about 9.2 anyway given our considerable recent expansions in the usage of WaitLatch.
* New 9.2 SSL parameters are GUC, not libpq, per Magnus's observation.Bruce Momjian2012-05-10
|
* Add 9.2 release note suggestions from Heikki,Bruce Momjian2012-05-10
|
* Python 2.2 is no longer supportedPeter Eisentraut2012-05-10
| | | | | | | It was already on its last legs, and it turns out that it was accidentally broken in commit 89e850e6fda9e4e441712012abe971fe938d595a and no one cared. So remove the rest the support for it and update the documentation to indicate that Python 2.3 is now required.
* Whitespace cleanupPeter Eisentraut2012-05-10
|
* 9.2 release note adjustments from Robert Haas.Bruce Momjian2012-05-10
|
* Another doc fix for HTML entities.Bruce Momjian2012-05-10
|
* Update entitiy escapes docs; must be Latin1.Bruce Momjian2012-05-10
|
* Remove URL that suggested numeric HTML entities.Bruce Momjian2012-05-10
|
* Remove unportable use of SGML character-code entity.Tom Lane2012-05-10
| | | | | | It'd be nice to be able to spell Jan Urbanski's name with the correct accent marks, but we haven't yet found a way that works in everybody's docs toolchain. This way definitely doesn't.
* Release notes adjustments from Erik RijkersBruce Momjian2012-05-10
|
* Improve two 9.2 release note items.Bruce Momjian2012-05-10
|
* Fix a couple of typos in 9.2 release notes.Heikki Linnakangas2012-05-10
| | | | Thom Brown
* Copy-editing 9.2 release notes.Heikki Linnakangas2012-05-10
| | | | | Fix a couple of typos, add missing filename tags, and add a link to the doc section on timezone guc.
* Only attempt to show collations on servers >= 9.1.Magnus Hagander2012-05-10
| | | | | | Show a proper error message instead of a SQL error. Josh Kupershmidt
* Fix outdated comment.Heikki Linnakangas2012-05-10
| | | | | Multi-insert records observe XLOG_HEAP_INIT_PAGE flag too, as Andres Freund pointed out.
* PL/pgSQL RETURN NEXT was leaking converted tuples, causingJoe Conway2012-05-09
| | | | | | out of memory when looping through large numbers of rows. Flag the converted tuples to be freed. Complaint and patch by Joe.
* Improve tests for postmaster death in auxiliary processes.Tom Lane2012-05-10
| | | | | | | | | | | | | In checkpointer and walwriter, avoid calling PostmasterIsAlive unless WaitLatch has reported WL_POSTMASTER_DEATH. This saves a kernel call per iteration of the process's outer loop, which is not all that much, but a cycle shaved is a cycle earned. I had already removed the unconditional PostmasterIsAlive calls in bgwriter and pgstat in previous patches, but forgot that WL_POSTMASTER_DEATH is supposed to be treated as untrustworthy (per comment in unix_latch.c); so adjust those two cases to match. There are a few other places where the same idea might be applied, but only after substantial code rearrangement, so I didn't bother.
* Update 9.2 SSL release note links.Bruce Momjian2012-05-10
|
* Further tweaking of nomenclature in checkpointer.c.Tom Lane2012-05-10
| | | | | | Get rid of some more naming choices that only make sense if you know that this code used to be in the bgwriter, as well as some stray comments referencing the bgwriter.
* Improve control logic for bgwriter hibernation mode.Tom Lane2012-05-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 6d90eaaa89a007e0d365f49d6436f35d2392cfeb added a hibernation mode to the bgwriter to reduce the server's idle-power consumption. However, its interaction with the detailed behavior of BgBufferSync's feedback control loop wasn't very well thought out. That control loop depends primarily on the rate of buffer allocation, not the rate of buffer dirtying, so the hibernation mode has to be designed to operate only when no new buffer allocations are happening. Also, the check for whether the system is effectively idle was not quite right and would fail to detect a constant low level of activity, thus allowing the bgwriter to go into hibernation mode in a way that would let the cycle time vary quite a bit, possibly further confusing the feedback loop. To fix, move the wakeup support from MarkBufferDirty and SetBufferCommitInfoNeedsSave into StrategyGetBuffer, and prevent the bgwriter from entering hibernation mode unless no buffer allocations have happened recently. In addition, fix the delaying logic to remove the problem of possibly not responding to signals promptly, which was basically caused by trying to use the process latch's is_set flag for multiple purposes. I can't prove it but I'm suspicious that that hack was responsible for the intermittent "postmaster does not shut down" failures we've been seeing in the buildfarm lately. In any case it did nothing to improve the readability or robustness of the code. In passing, express the hibernation sleep time as a multiplier on BgWriterDelay, not a constant. I'm not sure whether there's any value in exposing the longer sleep time as an independently configurable setting, but we can at least make it act like this for little extra code.
* Publish draft version of Postgres 9.2 release notes.Bruce Momjian2012-05-09
|
* Add make dependency so that postgres.bki is rebuilt in major version changePeter Eisentraut2012-05-09
| | | | | | | | | | | | | | | Every time since the current rule for postgres.bki was put in place when we change the major version, people complain that their tests fail in strange ways. This is because the version number in postgres.bki is not updated, because it has no dependency for that. And you can't even force the rebuild manually if you don't happen to know which file has the problem. Fix that now before it will happen again. The only remaining problem with switching major versions, as far as the regression tests are concerned, is that contrib needs to be rebuilt. But that's easily invoked, and in any case the failure modes are more friendly if you forget that.
* Split contrib documentation into extensions and programsPeter Eisentraut2012-05-09
| | | | | | | Create separate appendixes for contrib extensions and other server plugins on the one hand, and utility programs on the other. Recast the documentation of the latter as refentries, so that man pages are generated.
* Update documentation to say that gmake check in contrib is supportedPeter Eisentraut2012-05-09
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 01:15:09 +0000