aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* doc: Add missing backend_type to pg_stat_activityDaniel Gustafsson2023-05-30
| | | | | | | | | Commit 0c679464a8 added the missing backendDesc for B_STANDALONE_BACKEND but missed updating the list of backend types in the documentation. Fix by adding it to the list. Author: Noriyoshi Shinoda <noriyoshi.shinoda@hpe.com> Discussion: https://postgr.es/m/DM4PR84MB1734ECEA02BCB59564E8FC03EE4A9@DM4PR84MB1734.NAMPRD84.PROD.OUTLOOK.COM
* doc: PG 16 relnotes: adjust outer/full hash join parallelizationBruce Momjian2023-05-29
| | | | | | Reported-by: David Rowley Discussion: https://postgr.es/m/CAApHDvph4djrP+zjOK67VcgbB_p9Zn8QoO7Qctt4oQgUC_ejEw@mail.gmail.com
* doc: PG 16 relnotes, fix duplicate author and commitBruce Momjian2023-05-29
| | | | | | Reported-by: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoALE_joh=H-j5sdaAfDs=BXtCy6BQKYZBTi=neU8k0VFw@mail.gmail.com
* doc: PG 16 relnotes, fix "locale" typo and windows locale textBruce Momjian2023-05-27
| | | | | | Reported-by: Laurenz Albe, Álvaro Herrera Discussion: https://postgr.es/m/70a09a9fa557b632f4b1505395aaa6c4cb77b55a.camel@cybertec.at
* Doc fixes for commit 1e16af8ab5.Jeff Davis2023-05-25
| | | | Discussion: https://postgr.es/m/275c47ea-e7f3-e654-c99a-63bc116997d7@enterprisedb.com
* doc: fix typo in language tag documentationDaniel Gustafsson2023-05-25
| | | | Commit 1e16af8ab5 accidentally mistyped 'language' in one place.
* doc: Fix example query for pg_walinspectDaniel Gustafsson2023-05-25
| | | | | | | | | The LIMIT clause had ended up in the wrong place in the query. Backpatch to v15 where pg_walinspect was introduced. Reported-by: Jian He <jian.universality@gmail.com> Discussion: https://postgr.es/m/CACJufxHqXDr4NnmwmR6pEiVPAg54J0dgwMuYQzrH5BX6+NtF1g@mail.gmail.com Backpatch-through: 15
* doc: PG 16 relnotes, add author from previous mergeBruce Momjian2023-05-24
| | | | | | Reported-by: John Naylor Discussion: https://postgr.es/m/CAFBsxsEMoNdg6CCMuQ-6YJ8G=AgGNMVuiTb5Di5bsoPfBb=9CA@mail.gmail.com
* doc: PG 16 relnotes, wording adjustmentsBruce Momjian2023-05-24
| | | | | | Reported-by: Erik Rijkers Discussion: https://postgr.es/m/c4a88acf-ab1a-a912-d4a9-5e19b323c5ed@xs4all.nl
* doc: PG 16 relnotes, merge and move vector itemsBruce Momjian2023-05-24
| | | | | | Reported-by: John Naylor Discussion: https://postgr.es/m/CAFBsxsEPg8L2MmGqavc8JByC=WF_Mnkhn-KKnFPkcqh0hydung@mail.gmail.com
* doc: PG 16 relnotes, update xid/subxid searches itemBruce Momjian2023-05-24
| | | | | | Reported-by: John Naylor Discussion: https://postgr.es/m/CAFBsxsEPg8L2MmGqavc8JByC=WF_Mnkhn-KKnFPkcqh0hydung@mail.gmail.com
* Document deprecated createuser option.Nathan Bossart2023-05-23
| | | | | | | | | | | | 2dcd1578c4 left the --role option undocumented, which is inconsistent with other deprecated options such as pg_dump's --blobs and --no-blobs. This change adds --role back to createuser's documentation and usage output and marks it as deprecated. Suggested-by: Peter Eisentraut Reviewed-by: Michael Paquier Discussion: https://postgr.es/m/0e85c9e7-4804-1cdb-5a4a-c72c328f9ad8%40enterprisedb.com
* doc: PG 16 relnotes, SIMD improvementsBruce Momjian2023-05-23
| | | | | | Reported-by: John Naylor Discussion: https://postgr.es/m/CAFBsxsEuAx4_nq=200u=70S5r83C2hzO-a9+c6YXTCbOFeDAfw@mail.gmail.com
* doc: PG 16 relnotes, add major features listBruce Momjian2023-05-22
| | | | | | Reported-by: Jonathan Katz Discussion: https://postgr.es/m/2fd2cc0e-df39-3e77-8fcf-35aad5796b0a@postgresql.org
* Spell the values of libpq's gssdelegation parameter as "0" and "1".Tom Lane2023-05-22
| | | | | | | | | | | | | That's how other boolean options are handled, so do likewise. The previous coding with "enable" and "disable" was seemingly modeled on gssencmode, but that's a three-way flag. While at it, add PGGSSDELEGATION to the set of environment variables cleared by pg_regress and Utils.pm. Abhijit Menon-Sen, per gripe from Alvaro Herrera Discussion: https://postgr.es/m/20230522091609.nlyuu4nolhycqs2p@alvherre.pgsql
* doc: PG 16 relnotes, improve desc. of pg_log_standby_snapshot()Bruce Momjian2023-05-22
|
* pg_dump doc: mention 'long' is valid for --compressAlvaro Herrera2023-05-22
| | | | Apparently an oversight in 2820adf7755d.
* doc: PG 16 relnotes, improve description of standby log. decodeBruce Momjian2023-05-21
| | | | Improve description of "Allow logical decoding on standbys".
* Rename some createuser options.Nathan Bossart2023-05-21
| | | | | | | | | | | | This change renames --admin to --with-admin, --role to --member-of, and --member to --with-member. Many people found the previous names to be confusing. The --admin and --member options are new in v16, but --role has been there for a while, so that one has been kept (but left undocumented) for backward compatibility. Suggested-by: Peter Eisentraut Reviewed-by: Tom Lane, Michael Paquier Discussion: https://postgr.es/m/ZFvVZvQDliIWmOwg%40momjian.us
* doc: PG 16 relnotes, misc merged items and bootstrap detailBruce Momjian2023-05-21
| | | | | | Reported-by: Andres Freund, jian he Discussion: https://postgr.es/m/20230521171341.jjxykfsefsek4kzj@awork3.anarazel.de, 20230521171341.jjxykfsefsek4kzj@awork3.anarazel.de
* doc: PG 16 relnotes, misc. updatesBruce Momjian2023-05-21
| | | | | | Reported-by: Tom Lane Discussion: https://postgr.es/m/277016.1684689065@sss.pgh.pa.us
* doc: PG 16 relnotes, add commitsBruce Momjian2023-05-21
| | | | | | Reported-by: Ian Lawrence Barwick Discussion: https://postgr.es/m/CAB8KJ=hLvQDb53WdigV7OBEBh5tzQ7eA=pG0ZpccoRVBUNCXYA@mail.gmail.com
* Doc: fix some rendering problems in the PDF docs build.Tom Lane2023-05-21
| | | | | | | | Tweak column widths in a couple of tables to avoid "contents ... exceed the available area" warnings. Remove usage of some non-Latin-1 characters. Discussion: https://postgr.es/m/614600.1684537037@sss.pgh.pa.us
* Expand some more uses of "deleg" to "delegation" or "delegated".Tom Lane2023-05-21
| | | | | | | | | | Complete the task begun in 9c0a0e2ed: we don't want to use the abbreviation "deleg" for GSS delegation in any user-visible places. (For consistency, this also changes most internal uses too.) Abhijit Menon-Sen and Tom Lane Discussion: https://postgr.es/m/949048.1684639317@sss.pgh.pa.us
* Fix remaining references to gss_accept_deleg.Nathan Bossart2023-05-20
| | | | | | These were missed in 9c0a0e2ed9. Discussion: https://postgr.es/m/20230521031757.GA3835667%40nathanxps13
* rename "gss_accept_deleg" to "gss_accept_delegation".Bruce Momjian2023-05-20
| | | | | | This is more consistent with existing GUC spelling. Discussion: https://postgr.es/m/ZGdnEsGtNj7+fZoa@momjian.us
* doc: PG 16 relnotes, misc updatesBruce Momjian2023-05-20
| | | | | | | | | | | * document to_reg* accepting OIDs * document pg_log_standby_snapshot() * document pg_input_is_valid() and pg_input_error_info() * handle rename of function to pg_split_walfile_name() * fix character encoding problem for Przemyslaw Sztoch * remove partition section Reported-by: jian he, Tom Lane, Bertrand Drouvot
* Pre-beta mechanical code beautification.Tom Lane2023-05-19
| | | | | | | | | | | | | | | Run pgindent, pgperltidy, and reformat-dat-files. This set of diffs is a bit larger than typical. We've updated to pg_bsd_indent 2.1.2, which properly indents variable declarations that have multi-line initialization expressions (the continuation lines are now indented one tab stop). We've also updated to perltidy version 20230309 and changed some of its settings, which reduces its desire to add whitespace to lines to make assignments etc. line up. Going forward, that should make for fewer random-seeming changes to existing code. Discussion: https://postgr.es/m/20230428092545.qfb3y5wcu4cm75ur@alvherre.pgsql
* doc: PG 16 relnotes, delete reverted grant, adjust version numBruce Momjian2023-05-19
| | | | Reported-by: Nathan Bossart, Sehrope Sarkuni
* doc: PG 16 relnotes, merge REINDEX and reindexdb itemsBruce Momjian2023-05-19
| | | | Reported-by: Vibhor Kumar
* doc: PG 16 relnotes, add missing parenthesesBruce Momjian2023-05-19
| | | | Reported-by: Hans Buschmann
* pageinspect: Fix gist_page_items() with included columnsMichael Paquier2023-05-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Non-leaf pages of GiST indexes contain key attributes, leaf pages contain both key and non-key attributes, and gist_page_items() ignored the handling of non-key attributes. This caused a few problems when using gist_page_items() on a GiST index with INCLUDE: - On a non-leaf page, the function would crash. - On a leaf page, the function would work, but miss to display all the values for included attributes. This commit fixes gist_page_items() to handle such cases in a more appropriate way, and now displays the values of key and non-key attributes for each item separately in a style consistent with what ruleutils.c would generate for the attribute list, depending on the page type dealt with. In a way similar to how a record is displayed, values would be double-quoted for key or non-key attributes if required. ruleutils.c did not provide a routine able to control if non-key attributes should be displayed, so an extended() routine for index definitions is added to work around the leaf and non-leaf page differences. While on it, this commit fixes a third problem related to the amount of data reported for key attributes. The code originally relied on BuildIndexValueDescription() (used for error reports on constraints) that would not print all the data stored in the index but the index opclass's input type, so this limited the amount of information available. This switch makes gist_page_items() much cheaper as there is no need to run ACL checks for each item printed, which is not an issue anyway as superuser rights are required to execute the functions of pageinspect. Opclasses whose data cannot be displayed can rely on gist_page_items_bytea(). The documentation of this function was slightly incorrect for the output results generated on HEAD and v15, so adjust it on these branches. Author: Alexander Lakhin, Michael Paquier Discussion: https://postgr.es/m/17884-cb8c326522977acb@postgresql.org Backpatch-through: 14
* doc: improve pg_walinspect and role membership itemsBruce Momjian2023-05-18
| | | | Reported-by: Peter Geoghegan
* doc: improve description of adding roles as membersBruce Momjian2023-05-18
| | | | Discussion: https://postgr.es/m/ZFvVZvQDliIWmOwg@momjian.us
* doc: update PG 16 relnotes for pg_walinspect changesBruce Momjian2023-05-18
| | | | Reported-by: Peter Geoghegan
* Show empty BRIN ranges in brin_page_itemsTomas Vondra2023-05-19
| | | | | | | | | | Commit 3581cbdcd6 added a flag to identify empty BRIN ranges. This adds the new flag to brin_page_items() output. This is kept as a separate commit as it should not be backpatched. Reviewed-by: Justin Pryzby, Matthias van de Meent, Alvaro Herrera Discussion: https://postgr.es/m/402430e4-7d9d-6cf1-09ef-464d80afff3b@enterprisedb.com
* doc: PG 16 relnotes, add freeze and update walinspect itemsBruce Momjian2023-05-18
| | | | Reported-by: Peter Geoghegan
* docs: re-order some PG 16 relnotes itemsBruce Momjian2023-05-18
| | | | Reported-by: Jonathan Katz
* doc: more PG 16 relnote wording improvementsBruce Momjian2023-05-18
|
* doc: add more sections to PG 16 release notesBruce Momjian2023-05-18
|
* doc: first draft of the PG 16 release notesBruce Momjian2023-05-18
|
* Fix documentation build broken by 1e16af8ab5.Jeff Davis2023-05-18
|
* Doc improvements for language tags and custom ICU collations.Jeff Davis2023-05-18
| | | | | | | | | | | | | | Separate the documentation for language tags themselves from the available collation settings which can be included in a language tag. Include tables of the available options, more details about the effects of each option, and additional examples. Also include an explanation of the "levels" of textual features and how they relate to collation. Discussion: https://postgr.es/m/25787ec7-4c04-9a8a-d241-4dc9be0b1ba3@postgresql.org Reviewed-by: Jonathan S. Katz
* Reduce icu_validation_level default to WARNING.Jeff Davis2023-05-17
| | | | Discussion: https://postgr.es/m/daa9f060aa2349ebc84444515efece49e7b32c5d.camel@j-davis.com
* Add writeback to pg_stat_ioAndres Freund2023-05-17
| | | | | | | | | | | | | | | 28e626bde00 added the concept of IOOps but neglected to include writeback operations. ac8d53dae5 added time spent doing these I/O operations. Without counting writeback, checkpointer write time in the log often differed substantially from that in pg_stat_io. To fix this, add IOOp IOOP_WRITEBACK and track writeback in pg_stat_io. Bumps catversion. Author: Melanie Plageman <melanieplageman@gmail.com> Reviewed-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com> Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/20230419172326.dhgyo4wrrhulovt6%40awork3.anarazel.de
* Revert "Add USER SET parameter values for pg_db_role_setting"Alexander Korotkov2023-05-17
| | | | | | | | | This reverts commit 096dd80f3ccc and its fixups beecbe8e5001, afdd9f7f0e00, 529da086ba, db93e739ac61. Catversion is bumped. Discussion: https://postgr.es/m/d46f9265-ff3c-6743-2278-6772598233c2%40pgmasters.net
* doc: Fix ordering of entries in wait event table for I/O typeMichael Paquier2023-05-16
| | | | | | Issue spotted while reviewing a different patch touching this area. Discussion: https://postgr.es/m/ZGM1U5D5EuBUbasi@paquier.xyz
* doc: Fix incorrect version list for Windows SDKMichael Paquier2023-05-15
| | | | | | | | References to SDK 8.1a should have been cleaned up in 495ed0e, as only version 10 and above are supported with Windows 10 and newer versions. Reported-by: Thomas Munro Discussion: https://postgr.es/m/CA+hUKG++qE9uVjQaTTD7oaC8a2T3h8K50=Eqyx9uUZvOHa__ww@mail.gmail.com
* Rename io_direct to debug_io_direct.Thomas Munro2023-05-15
| | | | | | | | | | | | | | | | | | Give the new GUC introduced by d4e71df6 a name that is clearly not intended for mainstream use quite yet. Future proposals would drop the prefix only after adding infrastructure to make it efficient. Having the switch in the tree sooner is good because it might lead to new discoveries about the hazards awaiting us on a wide range of systems, but that name was too enticing and could lead to cross-version confusion in future, per complaints from Noah and Justin. Suggested-by: Noah Misch <noah@leadboat.com> Reviewed-by: Noah Misch <noah@leadboat.com> Reviewed-by: Justin Pryzby <pryzby@telsasoft.com> (the idea, not the patch) Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> (ditto) Discussion: https://postgr.es/m/20230430041106.GA2268796%40rfd.leadboat.com
* Tighten usage of PSQL_WATCH_PAGER.Tom Lane2023-05-12
| | | | | | | | | | | | | | | | | | | | | | Don't use PSQL_WATCH_PAGER when stdin/stdout are not a terminal. This corresponds to the restrictions on when other commands will use [PSQL_]PAGER. There isn't a lot of sense in trying to use a pager in non-interactive cases, and doing so allows an environment setting to break our tests. Also, ignore PSQL_WATCH_PAGER if it is set but empty or all-blank, for the same reasons we ignore such settings of [PSQL_]PAGER (see commit 18f8f784c). No documentation change is really needed, since there is nothing suggesting that these constraints on [PSQL_]PAGER didn't already apply to PSQL_WATCH_PAGER too. But I rearranged the text a little to make it read more naturally (IMHO anyway). Per report from Pavel Stehule. Back-patch to v15 where PSQL_WATCH_PAGER was introduced. Discussion: https://postgr.es/m/CAFj8pRDTwFzmEWdA-gdAcUh0ZnxUioSfTMre71WyB_wNJy-8gw@mail.gmail.com
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-17 07:25:15 +0000