summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2020-06-07doc: Fix man page whitespace issuesPeter Eisentraut
Whitespace between tags is significant, and in some cases it creates extra vertical space in man pages. The fix is either to remove some newlines or in some cases to reword slightly to avoid the awkward markup layout.
2020-06-07doc: Move options on man pages into more alphabetical orderPeter Eisentraut
2020-06-07doc: Fix up spacing around verbatim DocBook elementsPeter Eisentraut
2020-06-07doc: Language reviewPeter Eisentraut
2020-06-07doc: Trim trailing whitespacePeter Eisentraut
2020-06-07doc: Clean up title case usePeter Eisentraut
2020-06-07doc: Remove line breaks after <title>Peter Eisentraut
This creates unnecessary rendering problem risks, and it's inconsistent and gets copied around.
2020-06-07Doc: Clean up references to obsolete OS versions.Thomas Munro
Remove obsolete instructions for old operating system versions, and update the text to reflect the defaults on modern systems. Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Peter Eisentraut <peter.eisentraut@2ndquadrant.com> Reviewed-by: Magnus Hagander <magnus@hagander.net> Discussion: https://postgr.es/m/CA%2BhUKGLmJUSwybaPQv39rB8ABpqJq84im2UjZvyUY4feYhpWMw%40mail.gmail.com
2020-06-07doc: Fix incorrect link targetPeter Eisentraut
2020-06-06Fix reference to wrong view in release notesMagnus Hagander
The estimate of total backup size effects the view pg_stat_progress_basebackup, not pg_stat_progress_analyze.
2020-06-05Doc: remove annotations about multi-row output of set-returning functions.Tom Lane
I thought this added clarity, or at least was consistent with the way these entries looked before v13 ... but apparently I'm in the minority. Discussion: https://postgr.es/m/CAFj8pRAXuetiHUfs73zjsJD6B78FWcUsBS-j23sdCMFXkgx5Fg@mail.gmail.com
2020-06-04psql: Clean up terminology in \dAp commandPeter Eisentraut
The preferred terminology has been support "function", not procedure, for some time, so change that over. The command stays \dAp, since \dAf is already something else.
2020-06-02doc: PG 13 relnotes: fix link for grouping sets hash overflowBruce Momjian
Use "guc-enable-groupingsets-hash-disk". Reported-by: TAKATSUKA Haruka Discussion: https://postgr.es/m/16468-7939d39f1786516c@postgresql.org Backpatch-through: master
2020-06-03doc: Move wal_init_zero and wal_recycle descriptions to proper section.Fujii Masao
The group of wal_init_zero and wal_recycle is WAL_SETTINGS in guc.c, but previously their documents were located in "Replication"/"Sending Servers" section. This commit moves them to the proper section "Write Ahead Log"/"Settings". Back-patch to v12 where wal_init_zero and wal_recycle parameters were introduced. Author: Fujii Masao Discussion: https://postgr.es/m/b5190ab4-a169-6a42-0e49-aed0807c8976@oss.nttdata.com
2020-06-02Doc: Update the documentation for spilled transaction statistics.Amit Kapila
Reported-by: Sawada Masahiko Author: Sawada Masahiko, Amit Kapila Reviewed-by: Amit Kapila Discussion: https://postgr.es/m/CA+fd4k4vNg7dRO5ECHdtQXXf1=Q4M98pfLW0dU7BKD8h79pkqA@mail.gmail.com
2020-05-31Doc: Mention about caveats of --concurrently on reindexdb pageMichael Paquier
The documentation of REINDEX includes a complete description of CONCURRENTLY and its advantages as well as its disadvantages, but reindexdb was not really clear about all that. From discussion with Tom Lane, based on a report from Andrey Klychkov. Discussion: https://postgr.es/m/1590486572.205117372@f500.i.mail.ru Backpatch-through: 12
2020-05-29doc: Update the layout of "Viewing Statistics" section.Fujii Masao
This commit updates the "Viewing Statistics" section more like the existing catalogs chapter. - Change its layout so that an introductory paragrap is put above the table for each statistics view. Previously the explanations were below the tables. - Separate each view to different section and add index terms for them. Author: Fujii Masao Reviewed-by: Tom Lane Discussion: https://postgr.es/m/6f8a482c-b3fa-4ed9-21c3-6d222a2cb87d@oss.nttdata.com
2020-05-25doc: PG 13 relnotes: update bool_plperl itemBruce Momjian
Reported-by: Daniel Gustafsson Discussion: https://postgr.es/m/54F7560D-498A-4E51-BAA4-17D4AAB2AA57@yesql.se Backpatch-through: master
2020-05-25gss: add missing references to hostgssenc and hostnogssencBruce Momjian
These were missed when these were added to pg_hba.conf in PG 12; updates docs and pg_hba.conf.sample. Reported-by: Arthur Nascimento Bug: 16380 Discussion: https://postgr.es/m/20200421182736.GG19613@momjian.us Backpatch-through: 12
2020-05-25Doc: Fix order of pg_shmem_allocations in system view listMichael Paquier
pg_shmem_allocations was in the wrong position with pg_stats. Author: Ian Barwick Discussion: https://postgr.es/m/de7279d4-7ea0-037f-d7d2-1161682339db@2ndquadrant.com
2020-05-22doc: Add note about I/O timing information in EXPLAIN and pg_stat_database.Fujii Masao
Explain that the followings are tracked only when track_io_timing GUC is enabled. - blk_read_time and blk_write_time in pg_stat_database - time spent reading and writing data file blocks in EXPLAIN output with BUFFERS option Whther track_io_timing is enabled affects also blk_read_time and blk_write_time in pg_stat_statements, but which was already documented. Author: Atsushi Torikoshi Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/CACZ0uYHo_NwbxpLH76OGF-O=13tkR0ZM0zeyGEhZ+JEXZVRyCA@mail.gmail.com
2020-05-21doc: PG 13 relnotes: Improve FETCH linkBruce Momjian
Reported-by: Erwin Brandstetter Discussion: https://postgr.es/m/CAGHENJ4X626ZfYhondXSP4sQgC5zDtsp_LNg1QaD+U7vfgYXQQ@mail.gmail.com Backpatch-through: head
2020-05-21doc: PG 13 relnotes: fix FETCH FIRST ... WITH TIES xreflabelBruce Momjian
Reported-by: Erwin Brandstetter Discussion: https://postgr.es/m/CAGHENJ4X626ZfYhondXSP4sQgC5zDtsp_LNg1QaD+U7vfgYXQQ@mail.gmail.com Backpatch-through: head
2020-05-21doc: suggest 1.1 as a random_page_cost value for SSDsBruce Momjian
Reported-by: yigong hu Discussion: https://postgr.es/m/CAOxFffcourucFqSk+tZA13ErS3XRYkDy6EeaPff4AvHGiEEuug@mail.gmail.com Backpatch-through: 9.5
2020-05-21doc: Simplify mention of unique indexes for NULL controlBruce Momjian
Discussion: https://postgr.es/m/2304.1586532634@sss.pgh.pa.us Backpatch-through: 9.5
2020-05-21Doc: Describe CREATE INDEX deduplication strategy.Peter Geoghegan
The B-Tree index deduplication strategy used during CREATE INDEX and REINDEX differs from the lazy strategy used by retail inserts. Make that clear by adding a new paragraph to the B-Tree implementation section of the documentation. In passing, do some copy-editing of nearby deduplication documentation.
2020-05-20doc: Adding a partition does not require Access Exclusive lockAlvaro Herrera
This doc update was missed in 898e5e3290a7. Backpatch to 12. Pointed out by Pavel Luzanov Discussion: https://postgr.es/m/642e9fbc-b832-698b-9a8f-d626afd7014d@postgrespro.ru
2020-05-20Doc: Fix description of pg_class.relreplidentMichael Paquier
The description missed a comma and lacked an explanation of what happens with REPLICA IDENTITY USING INDEX when the dependent index is dropped. Author: Marina Polyakova Reviewed-by: Daniel Gustafsson, Michael Paquier Discussion: https://postgr.es/m/ad1a0badc32658b1bbb07aa312346a1d@postgrespro.ru Backpatch-through: 9.5
2020-05-20Doc: Replace reference to pg_stat_wal_receiver.received_lsn by flushed_lsnMichael Paquier
Oversight in 2c8dd05d, where the view's column has been renamed. Reported-by: Fujii Masao Discussion: https://postgr.es/m/c049ffcf-d2fe-90f7-c8ba-0741035aa6a7@oss.nttdata.com
2020-05-18doc: PG 13 relnotes: fix typosBruce Momjian
Reported-by: Daniel Gustafsson Discussion: https://postgr.es/m/0A9D816E-F49C-470B-A23F-8B4AF999382B@yesql.se
2020-05-16Fix more typos and grammar problems in the glossaryAlvaro Herrera
Author: Erik Rijkers <er@xs4all.nl> Discussion: https://postgr.es/m/508f2fb1764c3bd518ee96a4f2247d6f@xs4all.nl
2020-05-16Mop-up for wait event naming issues.Tom Lane
Synchronize the event names for parallel hash join waits with other event names, by getting rid of the slashes and dropping "-ing" suffixes. Rename ClogGroupUpdate to XactGroupUpdate, to match the new SLRU name. Move the ProcSignalBarrier event to the IPC category; it doesn't belong under IO. Also a bit more wordsmithing in the wait event documentation tables. Discussion: https://postgr.es/m/4505.1589640417@sss.pgh.pa.us
2020-05-17Make pg_stat_wal_receiver consistent with the WAL receiver's shmem infoMichael Paquier
d140f2f3 has renamed receivedUpto to flushedUpto, and has added writtenUpto to the WAL receiver's shared memory information, but pg_stat_wal_receiver was not consistent with that. This commit renames received_lsn to flushed_lsn, and adds a new column called written_lsn. Bump catalog version. Author: Michael Paquier Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/20200515090817.GA212736@paquier.xyz
2020-05-16Fix bugs in OpenSSL hook renaming.Tom Lane
libpq's exports.txt was overlooked in commit 36d108761, which the buildfarm is quite unhappy about. Also, I'd gathered that the plan included renaming PQgetSSLKeyPassHook to PQgetSSLKeyPassHook_OpenSSL, but that didn't happen in the patch as committed. I'm taking it on my own authority to do so now, since the window before beta1 is closing fast.
2020-05-16Rename PQsetSSLKeyPassHook and friendsAndrew Dunstan
4dc6355210 provided a way for libraries and clients to modify how libpq handles client certificate passphrases, by installing a hook. However, these routines are quite specific to how OpenSSL works, so it's misleading and not future-proof to have these names not refer to OpenSSL. Change all the names to add "_OpenSSL" after "Hook", and fix the docs accordingly. Author: Daniel Gustafsson Discussion: https://postgr.es/m/981DE552-E399-45C2-9F60-3F0E3770CC61@yesql.se
2020-05-16Fix typo in glossaryAlvaro Herrera
Reported privately by Justin Pryzby
2020-05-15Change locktype "speculative token" to "spectoken".Tom Lane
It's just weird that this name wasn't chosen to look like an identifier. The suspicion that it wasn't thought about too hard is reinforced by the fact that it wasn't documented in the pg_locks view (until I did so, a day or two back). Update, and add a comment reminding future adjusters of this array to fix the docs too. Do some desultory wordsmithing on various entries in the wait events tables. Discussion: https://postgr.es/m/24595.1589326879@sss.pgh.pa.us
2020-05-15Drop the redundant "Lock" suffix from LWLock wait event names.Tom Lane
This was mostly confusing, especially since some wait events in this class had the suffix and some did not. While at it, stop exposing MainLWLockNames[] as a globally visible name; any code using that directly is almost certainly wrong, as its name has been misleading for some time. (GetLWLockIdentifier() is what to use instead.) Discussion: https://postgr.es/m/28683.1589405363@sss.pgh.pa.us
2020-05-15Rename assorted LWLock tranches.Tom Lane
Choose names that fit into the conventions for wait event names (particularly, that multi-word names are in the style MultiWordName) and hopefully convey more information to non-hacker users than the previous names did. Also rename SerializablePredicateLockListLock to SerializablePredicateListLock; the old name was long enough to cause table formatting problems, plus the double occurrence of "Lock" seems confusing/error-prone. Also change a couple of particularly opaque LWLock field names. Discussion: https://postgr.es/m/28683.1589405363@sss.pgh.pa.us
2020-05-15Rename SLRU structures and associated LWLocks.Tom Lane
Originally, the names assigned to SLRUs had no purpose other than being shmem lookup keys, so not a lot of thought went into them. As of v13, though, we're exposing them in the pg_stat_slru view and the pg_stat_reset_slru function, so it seems advisable to take a bit more care. Rename them to names based on the associated on-disk storage directories (which fortunately we *did* think about, to some extent; since those are also visible to DBAs, consistency seems like a good thing). Also rename the associated LWLocks, since those names are likewise user-exposed now as wait event names. For the most part I only touched symbols used in the respective modules' SimpleLruInit() calls, not the names of other related objects. This renaming could have been taken further, and maybe someday we will do so. But for now it seems undesirable to change the names of any globally visible functions or structs, so some inconsistency is unavoidable. (But I *did* terminate "oldserxid" with prejudice, as I found that name both unreadable and not descriptive of the SLRU's contents.) Table 27.12 needs re-alphabetization now, but I'll leave that till after the other LWLock renamings I have in mind. Discussion: https://postgr.es/m/28683.1589405363@sss.pgh.pa.us
2020-05-15Review of the glossaryAlvaro Herrera
Add some more terms, clarify some definitions, remove redundant terms, move a couple of terms to keep alphabetical order. Co-authored-by: Jürgen Purtz <juergen@purtz.de> Co-authored-by: Erik Rijkers <er@xs4all.nl> Co-authored-by: Laurenz Albe <laurenz.albe@cybertec.at> Discussion: https://postgr.es/m/7b9b469e804777ac9df4d37716db935e@xs4all.nl
2020-05-15doc: PG 13 rels: use xref labels referencing ref/*.sgml filesBruce Momjian
This avoids using <link> and supplied text.
2020-05-15docs: add xreflabel entries for autovacuum, SP-GiST, and TOASTBruce Momjian
This is for use by the PG 13 release notes, but might be used for minor release notes in the future. Backpatch-through: 9.5
2020-05-15doc: add missing xreflabels to the main docs (not refs)Bruce Momjian
Add missing xreflabels for index types, geqo, libpq, spi, server-side languages, ecpg, and vaacuumlo. Backpatch-through: 9.5
2020-05-15doc: PG 13 relnotes: adjust UUID item, againBruce Momjian
2020-05-15doc: PG 13 relnotes: fix uuid itemBruce Momjian
2020-05-15doc: PG 13 relnotes: final SGML indenting adjustmentsBruce Momjian
2020-05-15doc: remove extra blank line at the top of SGML filesBruce Momjian
Backpatch-through: 9.5
2020-05-15doc: make ref/*.sgml file header comment layout consistentBruce Momjian
2020-05-15doc: PG 13 relnotes: fix xref link and remove extra wordBruce Momjian
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-30 23:17:40 +0000