summaryrefslogtreecommitdiff
path: root/doc/src/sgml/release-9.0.sgml
Commit message (Collapse)AuthorAgeFilesLines
* Doc: in each release branch, keep only that branch's own release notes.Tom Lane2019-02-041-11091/+0
| | | | | | | | | | | | | | | | | | | Historically we've had each release branch include all prior branches' notes, including minor-release changes, back to the beginning of the project. That's basically an O(N^2) proposition, and it was starting to catch up with us: as of HEAD the back-branch release notes alone accounted for nearly 30% of the documentation. While there's certainly some value in easy access to back-branch notes, this is getting out of hand. Hence, switch over to the rule that each branch contains only its own release notes. So as to not make older notes too hard to find, each branch will provide URLs for the immediately preceding branches' release notes on the project website. There might be value in providing aggregated notes across all branches somewhere on the website, but that's a task for another day. Discussion: https://postgr.es/m/cbd4aeb5-2d9c-8b84-e968-9e09393d4c83@postgresql.org
* Convert documentation to DocBook XMLPeter Eisentraut2017-11-231-43/+43
| | | | | | | | | | | | | | | | | | Since some preparation work had already been done, the only source changes left were changing empty-element tags like <xref linkend="foo"> to <xref linkend="foo"/>, and changing the DOCTYPE. The source files are still named *.sgml, but they are actually XML files now. Renaming could be considered later. In the build system, the intermediate step to convert from SGML to XML is removed. Everything is build straight from the source files again. The OpenSP (or the old SP) package is no longer needed. The documentation toolchain instructions are updated and are much simpler now. Peter Eisentraut, Alexander Lakhin, Jürgen Purtz
* Convert another SGML ID to lower casePeter Eisentraut2017-10-211-1/+1
| | | | | | The mostly automated conversion in 1ff01b3902cbf5b22d1a439014202499c21b2994 missed this one because of the unusual whitespace.
* Convert SGML IDs to lower casePeter Eisentraut2017-10-201-43/+43
| | | | | | | | | | | | | | IDs in SGML are case insensitive, and we have accumulated a mix of upper and lower case IDs, including different variants of the same ID. In XML, these will be case sensitive, so we need to fix up those differences. Going to all lower case seems most straightforward, and the current build process already makes all anchors and lower case anyway during the SGML->XML conversion, so this doesn't create any difference in the output right now. A future XML-only build process would, however, maintain any mixed case ID spellings in the output, so that is another reason to clean this up beforehand. Author: Alexander Lakhin <exclusion@gmail.com>
* Don't use SGML empty tagsPeter Eisentraut2017-10-171-1286/+1286
| | | | | | | | For DocBook XML compatibility, don't use SGML empty tags (</>) anymore, replace by the full tag name. Add a warning option to catch future occurrences. Alexander Lakhin, Jürgen Purtz
* Escape < and & in SGMLPeter Eisentraut2017-09-061-1/+1
| | | | | | | | | | | | This is not required in SGML, but will be in XML, so this is a step to prepare for the conversion to XML. (It is still not required to escape >, but we did it here in some cases for symmetry.) Add a command-line option to osx/onsgmls calls to warn about unescaped occurrences in the future. Author: Alexander Law <exclusion@gmail.com> Author: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
* doc: update markup for release note "release date" blockBruce Momjian2017-05-121-96/+96
| | | | | | | | | | | | | This has to be backpatched to all supported releases so release markup added to HEAD and copied to back branches matches the existing markup. Reported-by: Peter Eisentraut Discussion: 2b8a2552-fffa-f7c8-97c5-14db47a87731@2ndquadrant.com Author: initial patch and sample markup by Peter Eisentraut Backpatch-through: 9.2
* Spelling fixesPeter Eisentraut2017-03-141-1/+1
| | | | From: Josh Soref <jsoref@gmail.com>
* Refer to OS X as "macOS", except for the port name which is still "darwin".Tom Lane2016-09-251-4/+4
| | | | | | | | | | | | | | | | | | We weren't terribly consistent about whether to call Apple's OS "OS X" or "Mac OS X", and the former is probably confusing to people who aren't Apple users. Now that Apple has rebranded it "macOS", follow their lead to establish a consistent naming pattern. Also, avoid the use of the ancient project name "Darwin", except as the port code name which does not seem desirable to change. (In short, this patch touches documentation and comments, but no actual code.) I didn't touch contrib/start-scripts/osx/, either. I suspect those are obsolete and due for a rewrite, anyway. I dithered about whether to apply this edit to old release notes, but those were responsible for quite a lot of the inconsistencies, so I ended up changing them too. Anyway, Apple's being ahistorical about this, so why shouldn't we be?
* Adjust back-branch release note description of commits a2a718b22 et al.Tom Lane2016-01-021-2/+2
| | | | | | | | | As pointed out by Michael Paquier, recovery_min_apply_delay didn't exist in 9.0-9.3, making the release note text not very useful. Instead make it talk about recovery_target_xid, which did exist then. 9.0 is already out of support, but we can fix the text in the newer branches' copies of its release notes.
* Last-minute updates for release notes.Tom Lane2015-10-051-0/+22
| | | | | | Add entries for security and not-quite-security issues. Security: CVE-2015-5288, CVE-2015-5289
* Release notes for 9.5beta1, 9.4.5, 9.3.10, 9.2.14, 9.1.19, 9.0.23.Tom Lane2015-10-041-0/+475
|
* Release notes for 9.4.4, 9.3.9, 9.2.13, 9.1.18, 9.0.22.Tom Lane2015-06-091-0/+74
|
* Release notes for 9.4.3, 9.3.8, 9.2.12, 9.1.17, 9.0.21.Tom Lane2015-06-011-0/+101
| | | | | | Also sneak entries for commits 97ff2a564 et al into the sections for the previous releases in the relevant branches. Those fixes did go out in the previous releases, but missed getting documented.
* Last-minute updates for release notes.Tom Lane2015-05-191-10/+16
| | | | | | | Revise description of CVE-2015-3166, in line with scaled-back patch. Change release date. Security: CVE-2015-3166
* Last-minute updates for release notes.Tom Lane2015-05-181-0/+51
| | | | | | Add entries for security issues. Security: CVE-2015-3165 through CVE-2015-3167
* Release notes for 9.4.2, 9.3.7, 9.2.11, 9.1.16, 9.0.20.Tom Lane2015-05-171-0/+380
|
* Last-minute updates for release notes.Tom Lane2015-02-021-0/+85
| | | | | | Add entries for security issues. Security: CVE-2015-0241 through CVE-2015-0244
* Release notes for 9.4.1, 9.3.6, 9.2.10, 9.1.15, 9.0.19.Tom Lane2015-02-011-0/+641
|
* Release notes for 9.3.5, 9.2.9, 9.1.14, 9.0.18, 8.4.22.Tom Lane2014-07-211-6/+346
|
* Release notes for 9.3.4, 9.2.8, 9.1.13, 9.0.17, 8.4.21.Tom Lane2014-03-171-0/+156
|
* Last-minute updates for release notes.Tom Lane2014-02-171-0/+139
| | | | | | Add entries for security issues. Security: CVE-2014-0060 through CVE-2014-0067
* Release notes for 9.3.3, 9.2.7, 9.1.12, 9.0.16, 8.4.20.Tom Lane2014-02-161-0/+362
|
* Improve cross-references between minor version release notes.Tom Lane2014-02-121-11/+11
| | | | | | | | | | | | We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're using a browser or PDF reader, it's a lot nicer if it's a live hyperlink. So use "<xref>" instead. Any argument against doing this vanished with the recent decommissioning of plain-text release notes. Vik Fearing
* Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19.Tom Lane2013-12-021-0/+238
|
* Editorial corrections to the October 2013 minor-release notes.Tom Lane2013-11-301-22/+31
| | | | | | | | | | | This is mostly to fix incorrect migration instructions: since the preceding minor releases advised reindexing some GIST indexes, it's important that we back-link to that advice rather than earlier instances. Also improve some bug descriptions and fix a few typos. No back-patch yet; these files will get copied into the back branches later in the release process.
* doc: fix typo in release notesBruce Momjian2013-10-091-2/+2
| | | | | | Backpatch through 8.4 Per suggestion by Amit Langote
* docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1Bruce Momjian2013-10-071-0/+257
|
* Update release notes for 9.2.4, 9.1.9, 9.0.13, 8.4.17.Tom Lane2013-04-011-0/+14
| | | | Security: CVE-2013-1899, CVE-2013-1901
* Update release notes for changes through today.Tom Lane2013-03-311-1/+4
|
* Draft release notes for 9.2.4, 9.1.9, 9.0.13, 8.4.17.Tom Lane2013-03-281-0/+280
| | | | | Covers commits through today. Not back-patching into back branches yet, since this is just for people to review in advance.
* doc: Fix mistakes in the most recent set of release notes.Tom Lane2013-02-081-3/+3
| | | | | | | | | | Improve description of the vacuum_freeze_table_age bug (it's much more serious than we realized at the time the fix was committed), and correct attribution of pg_upgrade -O/-o fix (Marti Raudsepp contributed that, but Bruce forgot to credit him in the commit log). No need to back-patch right now, it'll happen when the next set of release notes are prepared.
* Prevent execution of enum_recv() from SQL.Tom Lane2013-02-041-0/+13
| | | | | | | | | | | | | | | | | This function was misdeclared to take cstring when it should take internal. This at least allows crashing the server, and in principle an attacker might be able to use the function to examine the contents of server memory. The correct fix is to adjust the system catalog contents (and fix the regression tests that should have caught this but failed to). However, asking users to correct the catalog contents in existing installations is a pain, so as a band-aid fix for the back branches, install a check in enum_recv() to make it throw error if called with a cstring argument. We will later revert this in HEAD in favor of correcting the catalogs. Our thanks to Sumit Soni (via Secunia SVCRP) for reporting this issue. Security: CVE-2013-0255
* Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.Tom Lane2013-02-041-0/+249
|
* Update release notes for 9.2.2, 9.1.7, 9.0.11, 8.4.15, 8.3.22.Tom Lane2012-12-031-0/+378
|
* Update release notes for 9.2.1, 9.1.6, 9.0.10, 8.4.14, 8.3.21.Tom Lane2012-09-191-0/+142
|
* Update release notes for 9.1.5, 9.0.9, 8.4.13, 8.3.20.Tom Lane2012-08-141-0/+306
|
* Update release notes for 9.1.4, 9.0.8, 8.4.12, 8.3.19.Tom Lane2012-05-311-0/+320
|
* Last-minute release note updates.Tom Lane2012-02-231-0/+50
| | | | Security: CVE-2012-0866, CVE-2012-0867, CVE-2012-0868
* Draft release notes for 9.1.3, 9.0.7, 8.4.11, 8.3.18.Tom Lane2012-02-221-0/+466
|
* Draft release notes for 9.1.2, 9.0.6, 8.4.10, 8.3.17, 8.2.23.Tom Lane2011-11-301-0/+384
|
* Update release notes for 9.1.1, 9.0.5, 8.4.9, 8.3.16, 8.2.22.Tom Lane2011-09-221-0/+650
| | | | Man, we fixed a lotta bugs since April.
* Update release notes for releases 9.0.4, 8.4.8, 8.3.15, and 8.2.21.Tom Lane2011-04-141-0/+344
|
* Clarify documentation for libpq's PQescapeBytea to mention the new hexBruce Momjian2011-02-131-1/+2
| | | | | | | | | | | | format. Modify PQescapeStringConn() docs to be consisent with other escaping functions. Add mention problems with pre-9.0 versions of libpq using not understanding bytea hex format to the 9.0 release notes. Backpatch to 9.0 docs.
* Back out libpq doc change; not ready yet.Bruce Momjian2011-02-131-2/+1
|
* Fix reverse 'if' test in path_is_relative_and_below_cwd(), per Tom.Bruce Momjian2011-02-131-1/+2
|
* Core support for "extensions", which are packages of SQL objects.Tom Lane2011-02-081-3/+2
| | | | | | | | | | | | | This patch adds the server infrastructure to support extensions. There is still one significant loose end, namely how to make it play nice with pg_upgrade, so I am not yet committing the changes that would make all the contrib modules depend on this feature. In passing, fix a disturbingly large amount of breakage in AlterObjectNamespace() and callers. Dimitri Fontaine, reviewed by Anssi Kääriäinen, Itagaki Takahiro, Tom Lane, and numerous others
* Properly capitalize documentation headings; some only had initial-wordBruce Momjian2011-01-291-4/+4
| | | | capitalization.
* Update release notes.Tom Lane2011-01-271-0/+13
| | | | Security: CVE-2010-4015
* Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20.Tom Lane2011-01-271-0/+163
|
View Lorry Controller Status