aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Doc: Replace reference to pg_stat_wal_receiver.received_lsn by flushed_lsnMichael Paquier2020-05-20
| | | | | | | 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
* doc: PG 13 relnotes: fix typosBruce Momjian2020-05-18
| | | | | | Reported-by: Daniel Gustafsson Discussion: https://postgr.es/m/0A9D816E-F49C-470B-A23F-8B4AF999382B@yesql.se
* Fix more typos and grammar problems in the glossaryAlvaro Herrera2020-05-16
| | | | | Author: Erik Rijkers <er@xs4all.nl> Discussion: https://postgr.es/m/508f2fb1764c3bd518ee96a4f2247d6f@xs4all.nl
* Mop-up for wait event naming issues.Tom Lane2020-05-16
| | | | | | | | | | | | 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
* Make pg_stat_wal_receiver consistent with the WAL receiver's shmem infoMichael Paquier2020-05-17
| | | | | | | | | | | | | 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
* Fix bugs in OpenSSL hook renaming.Tom Lane2020-05-16
| | | | | | | | | | 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.
* Rename PQsetSSLKeyPassHook and friendsAndrew Dunstan2020-05-16
| | | | | | | | | | | | | 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
* Fix typo in glossaryAlvaro Herrera2020-05-16
| | | | Reported privately by Justin Pryzby
* Change locktype "speculative token" to "spectoken".Tom Lane2020-05-15
| | | | | | | | | | | | | | | 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
* Drop the redundant "Lock" suffix from LWLock wait event names.Tom Lane2020-05-15
| | | | | | | | | | | | 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
* Rename assorted LWLock tranches.Tom Lane2020-05-15
| | | | | | | | | | | | | | | | 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
* Rename SLRU structures and associated LWLocks.Tom Lane2020-05-15
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Review of the glossaryAlvaro Herrera2020-05-15
| | | | | | | | | | 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
* doc: PG 13 rels: use xref labels referencing ref/*.sgml filesBruce Momjian2020-05-15
| | | | This avoids using <link> and supplied text.
* docs: add xreflabel entries for autovacuum, SP-GiST, and TOASTBruce Momjian2020-05-15
| | | | | | | 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
* doc: add missing xreflabels to the main docs (not refs)Bruce Momjian2020-05-15
| | | | | | | Add missing xreflabels for index types, geqo, libpq, spi, server-side languages, ecpg, and vaacuumlo. Backpatch-through: 9.5
* doc: PG 13 relnotes: adjust UUID item, againBruce Momjian2020-05-15
|
* doc: PG 13 relnotes: fix uuid itemBruce Momjian2020-05-15
|
* doc: PG 13 relnotes: final SGML indenting adjustmentsBruce Momjian2020-05-15
|
* doc: remove extra blank line at the top of SGML filesBruce Momjian2020-05-15
| | | | Backpatch-through: 9.5
* doc: make ref/*.sgml file header comment layout consistentBruce Momjian2020-05-15
|
* doc: PG 13 relnotes: fix xref link and remove extra wordBruce Momjian2020-05-15
|
* docs: PG 13 relnotes: add links and SGML formattingBruce Momjian2020-05-14
|
* Doc: hack on table 26.1 till it fits in PDF format.Tom Lane2020-05-14
| | | | | | | | | | | | | | | I abbreviated the heck out of the column headings, and made a few small wording changes, to get it to build warning-free. I can't say that the result is pretty, but it's probably better than removing this table entirely. As of this commit, we have zero "exceed the available area" warnings in a US-letter PDF build, and one such warning (about an 863-millipoint overrun) in an A4 build. I expect to get rid of that one by renaming wait events, so I'm not doing anything about it at the formatting level. Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
* Doc: tweak examples to silence line-too-long PDF build warnings.Tom Lane2020-05-14
| | | | | | | | | In one or two places it seemed reasonable to modify the example so as to shorten its output slightly; but for the most part I just added a &zwsp; after 67 characters, which is the most we can fit on a line of monospace text in A4 format. Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
* Initial pgindent and pgperltidy run for v13.Tom Lane2020-05-14
| | | | | | | | | | | Includes some manual cleanup of places that pgindent messed up, most of which weren't per project style anyway. Notably, it seems some people didn't absorb the style rules of commit c9d297751, because there were a bunch of new occurrences of function calls with a newline just after the left paren, all with faulty expectations about how the rest of the call would get indented.
* doc: PG 13 relnotes: move docbook version change to doc sect.Bruce Momjian2020-05-14
|
* Doc: Fix some inconsistencies with markupsMichael Paquier2020-05-14
| | | | | | | | This addresses some whitespace issues with programlisting, and corrects the spelling of "Enter PEM pass phrase" to be consistent with the code. Author: Daniel Gustafsson Discussion: https://postgr.es/m/401F9024-20EA-4239-83C4-6B7AD35F94BD@yesql.se
* Doc: split up wait_event table.Tom Lane2020-05-13
| | | | | | | | | | | | | | | | | | | | | | The previous design for this table didn't really work in narrow views, such as PDF output; besides which its reliance on large morerows values made it a pain to maintain (cf ab3e4fbd5, for example). I experimented with a couple of ways to fix it, but the best and simplest is to split it up into a separate table for each event type category. I also rearranged the event ordering to be strictly alphabetical, as nobody would ever be able to find entries otherwise. There is work afoot to revise the set of event names described in this table, but this commit just changes the layout, not the contents. In passing, add a missing entry to pg_locks.locktype, and cross-reference that to the related wait event list. Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
* Doc: reformat catalog/view description tables.Tom Lane2020-05-13
| | | | | | | | | | | This changes our catalog and view descriptions to use a style inspired by the new format for function/operator tables: each table entry is formatted roughly like a <varlistentry>, with the column name and type on the first line and then an indented description. This provides much more room for expansive descriptions than we had before, and thereby eliminates a passel of PDF build warnings. Discussion: https://postgr.es/m/12984.1588643549@sss.pgh.pa.us
* doc: PG 13 relnotes: adjust wal_skip_threshold wordingBruce Momjian2020-05-13
|
* docs: PG 13 relnotes: adjust wal_skip_threshold and UTF8 itemsBruce Momjian2020-05-12
|
* doc: PG 13 relnotes: add documentation section and reformatBruce Momjian2020-05-11
| | | | Add section about function table reformatting.
* Doc: hack table 13.2 "Conflicting Lock Modes" till it fits in PDF.Tom Lane2020-05-11
| | | | | | | | | | | | I can't see any way to make this table fit in PDF column width without either a fundamental redesign or abbreviating EXCLUSIVE. So I did the latter. It'd be nicer if the abbreviating didn't leak into the HTML output as well; but the hackery required to make the output different seems like more trouble than it's really worth. Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
* doc: PG 13 relnotes: add duplicate btree optimization detailsBruce Momjian2020-05-11
|
* doc: PG 13 relnotes: cumulative fixes from email feedbackBruce Momjian2020-05-11
|
* Doc: fix remaining over-length entries in SQL keywords table.Tom Lane2020-05-11
| | | | | | | | | | | | | | | | | | | Even after the tweaking I did in commit 5545b69ae, some of the longer keywords mentioned in the SQL standard don't fit the available space in PDF output. I experimented with various solutions like putting such keywords on their own table lines, but everything looked ugly or confusing or both; worse, the weirdness also appeared in the HTML version, which (normally) doesn't need it. The best answer seems to be to insert &zwsp; into long keywords so that they can be broken into two lines when, and only when, needed. It doesn't look too awful if the break happens after an underscore --- and fortunately, all the problematic keywords have underscores. Discussion: https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
* Doc: fix "Unresolved ID reference" warnings, clean up man page cross-refs.Tom Lane2020-05-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use xreflabel attributes instead of endterm attributes to control the appearance of links to subsections of SQL command reference pages. This is simpler, it matches what we do elsewhere (e.g. for GUC variables), and it doesn't draw "Unresolved ID reference" warnings from the PDF toolchain. Fix some places where the text was absolutely dependent on an <xref> rendering exactly so, by using a <link> around the required text instead. At least one of those spots had already been turned into bad grammar by subsequent changes, and the whole idea is just too fragile for my taste. <xref> does NOT have fixed output, don't write as if it does. Consistently include a page-level link in cross-man-page references, because otherwise they are useless/nonsensical in man-page output. Likewise, be consistent about mentioning "below" or "above" in same-page references; we were doing that in about 90% of the cases, but now it's 100%. Also get rid of another nonfunctional-in-PDF idea, of making cross-references to functions by sticking ID tags on <row> constructs. We can put the IDs on <indexterm>s instead --- which is probably not any more sensible in abstract terms, but it works where the other doesn't. (There is talk of attaching cross-reference IDs to most or all of the docs' function descriptions, but for now I just fixed the two that exist.) Discussion: https://postgr.es/m/14480.1589154358@sss.pgh.pa.us
* Doc: marginal hacking to remove some PDF build warnings.Tom Lane2020-05-10
| | | | | | | | | | | | | | This patch eliminates a few more "exceed the available area" warnings whose causes aren't particularly connected to anything else. The only one really worthy of comment is that I increased the space allowed for an <orderedlist>'s numbers, because the default of 1em doesn't quite work for more than one digit. The rest are one-off insertions of &zwsp; and suchlike tweaks, in places where they shouldn't do any damage to the material. (In particular, although I split some long identifiers with zwsp's, there are other nearby occurrences of each one; so those changes shouldn't hurt greppability of the document sources.)
* Doc: fix assorted misstatements of fact in catalog & system view docs.Tom Lane2020-05-09
| | | | | | | | I made up a very crude hack to compare the docs with reality (as embodied in the system catalogs) ... and indeed they don't match everywhere. Missing oid columns, wrong data types, wrong "references" links, columns listed in the wrong order. None of this seems quite important enough to back-patch.
* Fix several DDL issues of generated columns versus inheritancePeter Eisentraut2020-05-08
| | | | | | | | | | | | | | | | | | | | | | | | | | Several combinations of generated columns and inheritance in CREATE TABLE were not handled correctly. Specifically: - Disallow a child column specifying a generation expression if the parent column is a generated column. The child column definition must be unadorned and the parent column's generation expression will be copied. - Prohibit a child column of a generated parent column specifying default values or identity. - Allow a child column of a not-generated parent column specifying itself as a generated column. This previously did not work, but it was possible to arrive at the state via other means (involving ALTER TABLE), so it seems sensible to support it. Add tests for each case. Also add documentation about the rules involving generated columns and inheritance. Discussion: https://www.postgresql.org/message-id/flat/15830.1575468847%40sss.pgh.pa.us https://www.postgresql.org/message-id/flat/2678bad1-048f-519a-ef24-b12962f41807%40enterprisedb.com https://www.postgresql.org/message-id/flat/CAJvUf_u4h0DxkCMCeEKAWCuzGUTnDP-G5iVmSwxLQSXn0_FWNQ%40mail.gmail.com
* Fix inconsistency in pg_buffercache docs.Amit Kapila2020-05-08
| | | | | | | | | | | Commit 6e654546fb avoids locking bufmgr partitions to make pg_buffercache less disruptive on production systems but forgot to update the docs. Reported-by: Sawada Masahiko Author: Sawada Masahiko Reviewed-by: Amit Kapila Backpatch-through: 10 Discussion: https://postgr.es/m/CA+fd4k6sD8oeP1qJbFAor=rCpYckU9DsywHiYx3x5Hz5Z8Ua_w@mail.gmail.com
* Doc: update remaining tables of functions/operators for new layout.Tom Lane2020-05-07
| | | | | | | | | | | | This converts the contrib documentation to the new style, and mops up a couple of function tables that were outside chapter 9 in the main docs. A few contrib modules choose not to present their functions in the standard tabular format. There might be room to rethink those decisions now that the standard format is more friendly to verbose descriptions. But I have not undertaken to do that here; I just converted existing tables.
* doc: PG 13 relnotes: adjust partitioning itemsBruce Momjian2020-05-07
| | | | Reported-by: Amit Langote
* doc: PG 13 relnotes: adjust wording and Unicode itemBruce Momjian2020-05-07
|
* doc: PG 13 relnotes: adjust partition items and attributionsBruce Momjian2020-05-07
| | | | This merges three partition publication items into two.
* doc: PG 13 relnotes, update TOAST item to mention decompressionBruce Momjian2020-05-06
| | | | | | Reported-by: Andrey M. Borodin Discussion: https://postgr.es/m/D49B37B1-E2B9-4F67-8C6C-5CFD4015E8C5@yandex-team.ru
* pgbench: document that the default data loading is client-sideBruce Momjian2020-05-06
| | | | | | Reported-by: Fabien COELHO Discussion: https://postgr.es/m/alpine.DEB.2.22.394.2005051811320.2183756@pseudo
* Doc: remove now-redundant align specifications in colspecs.Tom Lane2020-05-06
| | | | | | In the wake of commit f21599311, we don't need to set table columns' align specs retail. Undo a few such settings I'd added in commit 5545b69ae. (The column width adjustments stay, though.)
* Doc: further fooling-about with rendering of tables in PDF output.Tom Lane2020-05-06
| | | | | | | | | | | | | | | | I concluded that we really just ought to force all tables in PDF output to default to "left" alignment (instead of "justify"); that is what the HTML toolchain does and that's what most people have been designing the tables to look good with. There are few if any places where "justify" produces better-looking output, and there are many where it looks horrible. So change stylesheet-fo.xsl to make that true. Also tweak column widths in a few more tables to make them look better and avoid "exceed the available area" warnings. This commit fixes basically everything that can be fixed through that approach. The remaining tables that give warnings either are scheduled for redesign as per recent discussions, or need a fundamental rethink because they Just Don't Work in a narrow view.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-01 16:08:11 +0000