aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* doc: Fix typosPeter Eisentraut2016-07-14
| | | | From: Alexander Law <exclusion@gmail.com>
* Fix obsolete header-file reference in pg_buffercache docs.Tom Lane2016-07-13
| | | | | | | Commit 2d0019049 moved enum ForkNumber from relfilenode.h into relpath.h, but missed updating this documentation reference. Alexander Law
* doc: Update URL for PL/PHPPeter Eisentraut2016-07-11
|
* Docs: improve examples about not repeating table name in UPDATE ... SET.Tom Lane2016-07-08
| | | | Alexander Law
* doc: mention dependency on collation librariesBruce Momjian2016-07-02
| | | | | | | | | | Document that index storage is dependent on the operating system's collation library ordering, and any change in that ordering can create invalid indexes. Discussion: 20160617154311.GB19359@momjian.us Backpatch-through: 9.1
* Document that dependency tracking doesn't consider function bodies.Tom Lane2016-06-21
| | | | | | | | | | | | | | | | | If there's anyplace in our SGML docs that explains this behavior, I can't find it right at the moment. Add an explanation in "Dependency Tracking" which seems like the authoritative place for such a discussion. Per gripe from Michelle Schwan. While at it, update this section's example of a dependency-related error message: they last looked like that in 8.3. And remove the explanation of dependency updates from pre-7.3 installations, which is probably no longer worth anybody's brain cells to read. The bogus error message example seems like an actual documentation bug, so back-patch to all supported branches. Discussion: <20160620160047.5792.49827@wrigleys.postgresql.org>
* Add missing documentation of pg_roles.rolbypassrlsMagnus Hagander2016-06-20
| | | | Noted by Lukas Fittl
* Docs: improve description of psql's %R prompt escape sequence.Tom Lane2016-06-19
| | | | | | | | | | | Dilian Palauzov pointed out in bug #14201 that the docs failed to mention the possibility of %R producing '(' due to an unmatched parenthesis. He proposed just adding that in the same style as the other options were listed; but it seemed to me that the sentence was already nearly unintelligible, so I rewrote it a bit more extensively. Report: <20160619121113.5789.68274@wrigleys.postgresql.org>
* Clarify documentation of ceil/ceiling/floor functions.Tom Lane2016-06-09
| | | | | | | | | | | | Document these as "nearest integer >= argument" and "nearest integer <= argument", which will hopefully be less confusing than the old formulation. New wording is from Matlab via Dean Rasheed. I changed the pg_description entries as well as the SGML docs. In the back branches, this will only affect installations initdb'd in the future, but it should be harmless otherwise. Discussion: <CAEZATCW3yzJo-NMSiQs5jXNFbTsCEftZS-Og8=FvFdiU+kYuSA@mail.gmail.com>
* Fix thinko in description of table_name parameterAlvaro Herrera2016-06-07
| | | | | | | | Commit 6820094d1 mixed up types of parent object (table) with type of sub-object being commented on. Noticed while fixing docs for COMMENT ON ACCESS METHOD. Backpatch to 9.5, like that commit.
* Fix typo in CREATE DATABASE syntax synopsis.Tom Lane2016-05-31
| | | | Misplaced "]", evidently a thinko in commit 213335c14.
* Fix typo in 9.5 release nodesAlvaro Herrera2016-05-26
| | | | Noted by 星合 拓馬 (HOSHIAI Takuma)
* Further improve documentation about --quote-all-identifiers switch.Tom Lane2016-05-20
| | | | | | Mention it in the Notes section too, per suggestion from David Johnston. Discussion: <20160520165824.22598.31426@wrigleys.postgresql.org>
* Improve documentation about pg_dump's --quote-all-identifiers switch.Tom Lane2016-05-20
| | | | | | | Per bug #14152 from Alejandro Martínez. Back-patch to all supported branches. Discussion: <20160520165824.22598.31426@wrigleys.postgresql.org>
* doc: Fix typoPeter Eisentraut2016-05-13
| | | | From: Alexander Law <exclusion@gmail.com>
* Release notes for 9.5.3, 9.4.8, 9.3.13, 9.2.17, 9.1.22.Tom Lane2016-05-07
|
* Docs: improve warnings about nextval() not producing gapless sequences.Tom Lane2016-05-07
| | | | | | | | | | | | | | In the documentation for nextval(), point out explicitly that INSERT ... ON CONFLICT will call nextval() if needed for the insertion case, whether or not it ends up following the ON CONFLICT path. This seems to be a matter of some confusion, cf bug #14126, so let's be clear about it. Also mention the issue in the CREATE SEQUENCE reference page, since that is another place where people might expect such things to be covered. Minor wording improvements nearby, as well. Back-patch to 9.5 where ON CONFLICT was introduced.
* Fix ordering/categorization of some recently-added system views.Tom Lane2016-05-05
| | | | | | | | | | | Somebody added pg_replication_origin, pg_replication_origin_status and pg_replication_slots to catalogs.sgml without a whole lot of concern for either alphabetical order or the difference between a table and a view. Clean up the mess. Back-patch to 9.5, not so much because this is critical as because if I don't it will result in a cross-branch divergence in release-9.5.sgml, which would be a maintenance hazard.
* doc: Fix more typosPeter Eisentraut2016-05-04
| | | | From: Alexander Law <exclusion@gmail.com>
* doc: Fix typosPeter Eisentraut2016-05-03
| | | | From: Alexander Law <exclusion@gmail.com>
* doc: Fix typoPeter Eisentraut2016-05-01
| | | | From: Guillaume Lelarge <guillaume@lelarge.info>
* Support building with Visual Studio 2015Andrew Dunstan2016-04-29
| | | | | | | | | | | Adjust the way we detect the locale. As a result the minumum Windows version supported by VS2015 and later is Windows Vista. Add some tweaks to remove new compiler warnings. Remove documentation references to the now obsolete msysGit. Michael Paquier, somewhat edited by me, reviewed by Christian Ullrich. Backpatch to 9.5
* doc: Fix typoPeter Eisentraut2016-04-24
| | | | From: Andreas Seltenreich <andreas.seltenreich@credativ.de>
* doc: Fix typosPeter Eisentraut2016-04-23
| | | | From: Erik Rijkers <er@xs4all.nl>
* doc: Add missing parenthesesPeter Eisentraut2016-04-15
| | | | From: Alexander Law <exclusion@gmail.com>
* Fix broken ALTER INDEX documentationAlvaro Herrera2016-04-05
| | | | | | | Commit b8a91d9d1c put the description of the new IF EXISTS clause in the wrong place -- move it where it belongs. Backpatch to 9.2.
* Remove TZ environment-variable entry from postgres reference page.Tom Lane2016-03-29
| | | | | | | | | | | | The server hasn't paid attention to the TZ environment variable since commit ca4af308c32d03db, but that commit missed removing this documentation reference, as did commit d883b916a947a3c6 which added the reference where it now belongs (initdb). Back-patch to 9.2 where the behavior changed. Also back-patch d883b916a947a3c6 as needed. Matthew Somerville
* Fix pgbench documentation error.Robert Haas2016-03-29
| | | | | | | | The description of what the per-transaction log file says for skipped transactions is just plain wrong. Report and patch by Tomas Vondra, reviewed by Fabien Coelho and modified by me.
* Mention BRIN as able to do multi-column indexesAlvaro Herrera2016-03-28
| | | | | | | | Documentation mentioned B-tree, GiST and GIN as able to do multicolumn indexes; I failed to add BRIN to the list. Author: Petr Jediný Reviewed-By: Fujii Masao, Emre Hasegeli
* Last-minute updates for release notes.Tom Lane2016-03-28
| | | | Security: CVE-2016-2193, CVE-2016-3065
* Release notes for 9.5.2, 9.4.7, 9.3.12, 9.2.16, 9.1.21.Tom Lane2016-03-27
|
* docs: Fix typo'd brin_summarize_new_valuesAlvaro Herrera2016-03-17
| | | | | | | | I wrote "brin_summarize_new_pages" instead, in docs as well as in the commit message of commit ac443d1034d9. Bug: #14030 Reported-By: Chris Pacejo
* Document BRIN a bit more thoroughlyAlvaro Herrera2016-03-10
| | | | | | | | | | | | The chapter "Interfacing Extensions To Indexes" and CREATE OPERATOR CLASS reference page were missed when BRIN was added. We document all our other index access methods there, so make sure BRIN complies. Author: Álvaro Herrera Reported-By: Julien Rouhaud, Tom Lane Reviewed-By: Emre Hasegeli Discussion: https://www.postgresql.org/message-id/56CF604E.9000303%40dalibo.com Backpatch: 9.5, where BRIN was introduced
* Update GetForeignPlan documentation.Robert Haas2016-03-08
| | | | | | | | Commit 385f337c9f39b21dca96ca4770552a10a6d5af24 added a new argument to the FDW GetForeignPlan method, but failed to update the documentation to match. Etsuro Fujita
* Fix minor typo in logical-decoding docs.Tom Lane2016-03-07
| | | | David Rowley
* Fix typosMagnus Hagander2016-03-06
| | | | Author: Guillaume Lelarge
* Ignore recovery_min_apply_delay until recovery has reached consistent stateFujii Masao2016-03-06
| | | | | | | | | | | | | | | | | | | Previously recovery_min_apply_delay was applied even before recovery had reached consistency. This could cause us to wait a long time unexpectedly for read-only connections to be allowed. It's problematic because the standby was useless during that wait time. This patch changes recovery_min_apply_delay so that it's applied once the database has reached the consistent state. That is, even if the delay is set, the standby tries to replay WAL records as fast as possible until it has reached consistency. Author: Michael Paquier Reviewed-By: Julien Rouhaud Reported-By: Greg Clough Backpatch: 9.4, where recovery_min_apply_delay was added Bug: #13770 Discussion: http://www.postgresql.org/message-id/20151111155006.2644.84564@wrigleys.postgresql.org
* doc: document MANPATH as /usr/local/pgsql/share/manAlvaro Herrera2016-02-29
| | | | | | | | | The docs were advising to use /usr/local/pgsql/man instead, but that's wrong. Reported-By: Slawomir Sudnik Backpatch-To: 9.1 Bug: #13894
* Fix wording in the Tutorial document.Tatsuo Ishii2016-02-21
| | | | With suggentions from Tom Lane.
* Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.Tom Lane2016-02-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dead or half-dead index leaf pages were incorrectly reported as live, as a consequence of a code rearrangement I made (during a moment of severe brain fade, evidently) in commit d287818eb514d431. The index metapage was not counted in index_size, causing that result to not agree with the actual index size on-disk. Index root pages were not counted in internal_pages, which is inconsistent compared to the case of a root that's also a leaf (one-page index), where the root would be counted in leaf_pages. Aside from that inconsistency, this could lead to additional transient discrepancies between the reported page counts and index_size, since it's possible for pgstatindex's scan to see zero or multiple pages marked as BTP_ROOT, if the root moves due to a split during the scan. With these fixes, index_size will always be exactly one page more than the sum of the displayed page counts. Also, the index_size result was incorrectly documented as being measured in pages; it's always been measured in bytes. (While fixing that, I couldn't resist doing some small additional wordsmithing on the pgstattuple docs.) Including the metapage causes the reported index_size to not be zero for an empty index. To preserve the desired property that the pgstattuple regression test results are platform-independent (ie, BLCKSZ configuration independent), scale the index_size result in the regression tests. The documentation issue was reported by Otsuka Kenji, and the inconsistent root page counting by Peter Geoghegan; the other problems noted by me. Back-patch to all supported branches, because this has been broken for a long time.
* Improve documentation about CREATE INDEX CONCURRENTLY.Tom Lane2016-02-16
| | | | | | | | | | | | | | Clarify the description of which transactions will block a CREATE INDEX CONCURRENTLY command from proceeding, and mention that the index might still not be usable after CREATE INDEX completes. (This happens if the index build detected broken HOT chains, so that pg_index.indcheckxmin gets set, and there are open old transactions preventing the xmin horizon from advancing past the index's initial creation. I didn't want to explain what broken HOT chains are, though, so I omitted an explanation of exactly when old transactions prevent the index from being used.) Per discussion with Chris Travers. Back-patch to all supported branches, since the same text appears in all of them.
* release notes: fix 9.5 SGML comment about commitBruce Momjian2016-02-16
| | | | | | Reported-by: Tatsuo Ishii Backpatch-through: 9.5
* Improve wording in the planner docTatsuo Ishii2016-02-16
| | | | | Change "In this case" to "In the example above" to clarify what it actually refers to.
* Correct the formulas for System V IPC parameters SEMMNI and SEMMNS in docs.Fujii Masao2016-02-16
| | | | | | | | | | | | | | | | | | | | | In runtime.sgml, the old formulas for calculating the reasonable values of SEMMNI and SEMMNS were incorrect. They have forgotten to count the number of semaphores which both the checkpointer process (introduced in 9.2) and the background worker processes (introduced in 9.3) need. This commit fixes those formulas so that they count the number of semaphores which the checkpointer process and the background worker processes need. Report and patch by Kyotaro Horiguchi. Only the patch for 9.3 was modified by me. Back-patch to 9.2 where the checkpointer process was added and the number of needed semaphores was increased. Author: Kyotaro Horiguchi Reviewed-by: Fujii Masao Backpatch: 9.2 Discussion: http://www.postgresql.org/message-id/20160203.125119.66820697.horiguchi.kyotaro@lab.ntt.co.jp
* Accept pg_ctl timeout from the PGCTLTIMEOUT environment variable.Noah Misch2016-02-10
| | | | | | | | | | | Many automated test suites call pg_ctl. Buildfarm members axolotl, hornet, mandrill, shearwater, sungazer and tern have failed when server shutdown took longer than the pg_ctl default 60s timeout. This addition permits slow hosts to easily raise the timeout without us editing a --timeout argument into every test suite pg_ctl call. Back-patch to 9.1 (all supported versions) for the sake of automated testing. Reviewed by Tom Lane.
* Last-minute updates for release notes.Tom Lane2016-02-08
| | | | Security: CVE-2016-0773
* Improve documentation about PRIMARY KEY constraints.Tom Lane2016-02-07
| | | | | | | | | | | Get rid of the false implication that PRIMARY KEY is exactly equivalent to UNIQUE + NOT NULL. That was more-or-less true at one time in our implementation, but the standard doesn't say that, and we've grown various features (many of them required by spec) that treat a pkey differently from less-formal constraints. Per recent discussion on pgsql-general. I failed to resist the temptation to do some other wordsmithing in the same area.
* Release notes for 9.5.1, 9.4.6, 9.3.11, 9.2.15, 9.1.20.Tom Lane2016-02-07
|
* Simplify syntax diagram for REINDEX.Tom Lane2016-02-04
| | | | | | | | Since there currently is only one possible parenthesized option, namely VERBOSE, it's a bit pointless to show it with "{ } [, ... ]". The curly braces are useless and therefore confusing, as seen in a recent question from Karsten Hilbert. Remove the extra decoration for the time being; we can put it back when and if REINDEX grows some more options.
* Add hstore_to_jsonb() and hstore_to_jsonb_loose() to hstore documentation.Tom Lane2016-02-03
| | | | These were never documented anywhere user-visible. Tut tut.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-22 04:51:28 +0000