aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* doc: PG 13 relnotes, fix markupBruce Momjian2020-05-05
|
* doc: PG 13 renotes: adjust attribution and pgbench itemBruce Momjian2020-05-05
|
* doc: PG 13 relnotes, add pgbench script itemBruce Momjian2020-05-05
|
* doc: PG 13 relnotes, add attributions and wording changesBruce Momjian2020-05-05
|
* Doc: warn that timezone abbreviations don't work in recovery_target_time.Tom Lane2020-05-05
| | | | | | | | | | | | | | | | | Moving this setting into the main configuration file was ill-considered, perhaps, because that typically causes it to be set before timezone_abbreviations has been set. Which in turn means that zone abbreviations don't work, only full zone names. We could imagine hacking things so that such cases do work, but the stability of the hack would be questionable, and the value isn't really that high. Instead just document that you should use a numeric zone offset or a full zone name. Per bug #16404 from Reijo Suhonen. Back-patch to v12 where this was changed. Discussion: https://postgr.es/m/16404-4603a99603fbd04c@postgresql.org
* doc: PG 13 release note adjustments, Justin Pryzby v2Bruce Momjian2020-05-05
| | | | Reported-by: Justin Pryzby
* doc: PG 13 retnote adjustmentsBruce Momjian2020-05-05
| | | | Reported-by: Justin Pryzby
* doc: normalize contributor names in PG 13 release notesBruce Momjian2020-05-05
|
* doc: update PG 13 release notes for glossary and NO DEPENDSBruce Momjian2020-05-05
|
* doc: Fix PG 13 release note markupBruce Momjian2020-05-05
|
* doc: update PG 13 release notes after first draftBruce Momjian2020-05-05
| | | | Minor corrections from individuals.
* Doc: Outline REPLICATION before SUPERUSER privilegeMichael Paquier2020-05-05
| | | | | | | | | | | | | | | The following docs are updated: - High-availaility section - pg_basebackup - pg_receivewal Per the principle of least privilege, we want to encourage users to interact with those areas using roles that have replication rights, but superusers were mentioned first. Author: Daniel Gustafsson Reviewed-by: Fujii Masao, Michael Paquier Discussion: https://postgr.es/m/ECEBD212-7101-41EB-84F3-2F356E4B6401@yesql.se
* doc: first draft of PG 13 release notesBruce Momjian2020-05-04
| | | | This still needs markup, indenting, and word wrap.
* Change the display of WAL usage statistics in Explain.Amit Kapila2020-05-05
| | | | | | | | | | | | | | | | In commit 33e05f89c5, we have added the option to display WAL usage statistics in Explain and auto_explain. The display format used two spaces between each field which is inconsistent with Buffer usage statistics which is using one space between each field. Change the format to make WAL usage statistics consistent with Buffer usage statistics. This commit also changed the usage of "full page writes" to "full page images" for WAL usage statistics to make it consistent with other parts of code and docs. Author: Julien Rouhaud, Amit Kapila Reviewed-by: Justin Pryzby, Kyotaro Horiguchi and Amit Kapila Discussion: https://postgr.es/m/CAB-hujrP8ZfUkvL5OYETipQwA=e3n7oqHFU=4ZLxWS_Cza3kQQ@mail.gmail.com
* Doc: improve PDF presentation of some tables by adjusting column widths.Tom Lane2020-05-04
| | | | | | | | | | | | | | | | | | | | The PDF toolchain defaults to laying out all columns of a table with equal widths, in contrast to the HTML rendering which automatically varies the column widths to fit the data. In many places, this results in very badly laid-out tables, with lots of useless whitespace in some places and text that overruns its cell in other places. For tables that have reasonably static content, we can improve matters by adding <colspec> entries to hand-assign the column widths. This commit does that for a few of the tables that were worst off; it eliminates close to 200 "contents ... exceed the available area" warnings in an A4 PDF build. I also forced align="left" in these tables, overriding the PDF toolchain's default which is evidently "justify". (The HTML toolchain seems to default to that already.) Anyplace where things are tight enough that we need to worry about this, forced justification tends to look truly awful.
* Doc: standardize markup a bit more.Tom Lane2020-05-04
| | | | | | | | | | | | | | | | We had a mishmash of <replaceable>, <replaceable class="parameter">, and <parameter> markup for operator/function arguments. Use <parameter> consistently for things that are in fact names of parameters (including OUT parameters), reserving <replaceable> for things that aren't. The latter class includes some made-up-by-the-docs type class names, like "numeric_type", as well as placeholders for arguments that don't have well-defined types. Possibly we could do better with those categories as well, but for the moment I'm content not to have parameter names marked up in different ways in different places. (This commit aligns the earlier sections of chapter 9 with a policy that I'd arrived at while working on commit 1ad23335f, which is why the last few sections need no changes.)
* Doc: update sections 9.22 - 9.30 for new function table layout.Tom Lane2020-05-04
| | | | With the usual quota of minor and less-minor editorial changes.
* Remove pg_xact from pg_stat_reset_slru docsTomas Vondra2020-05-02
| | | | | | | This should have been included in 2e08d314ed. Reported-by: Fujii Masao Discussion: https://postgr.es/m/20200119143707.gyinppnigokesjok@development
* Doc: update sections 9.17 - 9.21 for new function table layout.Tom Lane2020-05-01
| | | | With the usual quota of minor editorial changes.
* Improve various aspects of pg_rewind documentationMichael Paquier2020-05-01
| | | | | | | | | | | | | | | | | The pg_rewind docs currently assert that the state of the target's data directory after rewind is equivalent to the source's data directory. This clarifies the documentation to describe that the base state is further back in time and that the target's data directory will include the current state from the source of any copied blocks since the point of divergence. This commit also improves the section "How It Works": - Describe the update of the pg_control file. - Reorganize the list of files and directories ignored during the rewind. Author: James Coleman Discussion: https://postgr.es/m/CAAaqYe-sgqCos7MXF4XiY8rUPy3CEmaCY9EvfhX-DhPhPBF5_A@mail.gmail.com
* Doc: update sections 9.14 - 9.16 for new function table layout.Tom Lane2020-04-30
| | | | | Minor editorial changes in the first two sections; larger ones in the JSON section.
* Rename connection parameters to control min/max SSL protocol version in libpqMichael Paquier2020-04-30
| | | | | | | | | | | | | | The libpq parameters ssl{max|min}protocolversion are renamed to use underscores, to become ssl_{max|min}_protocol_version. The related environment variables still use the names introduced in commit ff8ca5f that added the feature. Per complaint from Peter Eisentraut (this was also mentioned by me in the original patch review but the issue got discarded). Author: Daniel Gustafsson Reviewed-by: Peter Eisentraut, Michael Paquier Discussion: https://postgr.es/m/b319e449-318d-e691-4997-1327e166fcc4@2ndquadrant.com
* Doc: re-re-revise markup for tables of functions.Tom Lane2020-04-30
| | | | | | | | | | | | | | | | Make the markup a bit less ad-hoc. A function-table cell now contains several <para> units, and we label the ones that contain function signatures with role="func_signature". The CSS or FO stylesheets then key off of that to decide how to set the indentation. A very useful win from this approach is that we can have more than one signature entry per table cell, simplifying the documentation of closely-related operators and functions. This patch mostly just replaces the markup in the tables I converted so far. But I did alter a couple of places where multiple signatures were helpful. Discussion: https://postgr.es/m/5561.1587922854@sss.pgh.pa.us
* Doc: render &pi; more nicely in PDF output.Tom Lane2020-04-27
| | | | | | | | We need to select symbol font explicitly, or it comes out misaligned. Alexander Lakhin, Tom Lane Discussion: https://postgr.es/m/10598.1587928415@sss.pgh.pa.us
* Doc: improve documentation of websearch_to_tqsuery().Tom Lane2020-04-26
| | | | | | | | | It wasn't totally clear about punctuation other than what's specified being ignored. Pavel Borisov and Tom Lane Discussion: https://postgr.es/m/CALT9ZEFsBdsogVjG40Z4KfM1Um=wj1FE9hJ00GK3oVfzz0sFNg@mail.gmail.com
* Doc: update section 9.13 for new function table layout.Tom Lane2020-04-24
| | | | | | | | | This includes the usual amount of editorial cleanup, such as correcting wrong or less-helpful-than-they-could-be examples. I moved the two tsvector-updating triggers into "9.28 Trigger Functions", which seems like a better home for them. (I believe that section didn't exist when this text was originally written.)
* Doc: update section 9.12 for new function table layout.Tom Lane2020-04-23
| | | | | | | | Also rearrange that page a bit for more consistency and less duplication. In passing, fix erroneous examples of the results of abbrev(cidr) in datatype.sgml, and do a bit of copy-editing there.
* Doc: improve description of geometric multiplication/division.Tom Lane2020-04-22
| | | | | | | | | | | | David Johnston reminded me that the per-point calculations being done by these operators are equivalent to complex multiplication/division. (Once I would've recognized that immediately, but it's been too long since I did any of that sort of math.) Also put in a footnote mentioning that "rotation" of a box doesn't do what you might expect, as I'd griped about in the referenced thread. Discussion: https://postgr.es/m/158110996889.1089.4224139874633222837@wrigleys.postgresql.org
* docs: land height is "elevation", not "altitude"Bruce Momjian2020-04-22
| | | | | | | | | | | See https://mapscaping.com/blogs/geo-candy/what-is-the-difference-between-elevation-relief-and-altitude No patching of regression tests. Reported-by: taf1@cornell.edu Discussion: https://postgr.es/m/158506544539.679.2278386310645558048@wrigleys.postgresql.org Backpatch-through: 9.5
* Doc: update section 9.11 for new function table layout.Tom Lane2020-04-22
| | | | | | | | | | | | | | | | This also makes an attempt to flesh out the docs for some of the more severely underdocumented geometric operators and functions. This effort exposed that the point <^ point (point_below) and point >^ point (point_above) operators are misnamed; they should be <<| and |>>, because they act like the other operators named that way and not like the other operators named <^ and >^. But I just documented them that way; fixing it is matter for another patch. The haphazard datatype coverage of many of the operators is also now depressingly obvious. Discussion: https://postgr.es/m/158110996889.1089.4224139874633222837@wrigleys.postgresql.org
* Document partitiong tables ancillary object handling some moreAlvaro Herrera2020-04-21
| | | | | | | | | | | Add a couple of lines to make it explicit that indexes, constraints, triggers are added, removed, or left alone. Backpatch to pg11. Author: Álvaro Herrera <alvherre@alvh.no-ip.org> Reviewed-by: Justin Pryzby <pryzby@telsasoft.com> Discussion: https://postgr.es/m/20200421162038.GA18628@alvherre.pgsql
* Fix detaching partitions with cloned row triggersAlvaro Herrera2020-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a partition is detached, any triggers that had been cloned from its parent were not properly disentangled from its parent triggers. This resulted in triggers that could not be dropped because they depended on the trigger in the trigger in the no-longer-parent table: ALTER TABLE t DETACH PARTITION t1; DROP TRIGGER trig ON t1; ERROR: cannot drop trigger trig on table t1 because trigger trig on table t requires it HINT: You can drop trigger trig on table t instead. Moreover the table can no longer be re-attached to its parent, because the trigger name is already taken: ALTER TABLE t ATTACH PARTITION t1 FOR VALUES FROM (1)TO(2); ERROR: trigger "trig" for relation "t1" already exists The former is a bug introduced in commit 86f575948c77. (The latter is not necessarily a bug, but it makes the bug more uncomfortable.) To avoid the complexity that would be needed to tell whether the trigger has a local definition that has to be merged with the one coming from the parent table, establish the behavior that the trigger is removed when the table is detached. Backpatch to pg11. Author: Justin Pryzby <pryzby@telsasoft.com> Reviewed-by: Amit Langote <amitlangote09@gmail.com> Reviewed-by: Álvaro Herrera <alvherre@alvh.no-ip.org> Discussion: https://www.postgresql.org/message-id/flat/20200408152412.GZ2228@telsasoft.com
* Mention pg_promote() as a method to trigger promotion in documentation.Fujii Masao2020-04-21
| | | | | | | | | | | | | Previously in the "Standby Server Operation" section, pg_ctl promote and protmote_trigger_file were documented as a method to trigger standby promotion, but pg_promote() function not. This commit also adds parentheses into <function>pg_promote</function> in some docs to make it clearer that a function is being referred to. Author: Masahiro Ikeda Reviewed-by: Michael Paquier, Laurenz Albe, Tom Lane, Fujii Masao Discussion: https://postgr.es/m/de0068417a9f4046bac693cbcc00bdc9@oss.nttdata.com
* doc: change SGML markup "figure" to "example"Bruce Momjian2020-04-20
| | | | | | | | | | Reported-by: Jürgen Purtz Discussion: https://postgr.es/m/709d7809-d7f4-8175-47f3-4d131341bba8@purtz.de Author: Jürgen Purtz Backpatch-through: 9.5
* Doc: update sections 9.7 and 9.8 for new function table layout.Tom Lane2020-04-20
| | | | Also some mop-up in section 9.9.
* Add ALTER .. NO DEPENDS ONAlvaro Herrera2020-04-20
| | | | | | | | | | | | | | Commit f2fcad27d59c (9.6 era) added the ability to mark objects as dependent an extension, but forgot to add a way for such dependencies to be removed. This commit fixes that oversight. Strictly speaking this should be backpatched to 9.6, but due to lack of demand we're not doing so at this time. Discussion: https://postgr.es/m/20200217225333.GA30974@alvherre.pgsql Reviewed-by: ahsan hadi <ahsan.hadi@gmail.com> Reviewed-by: Ibrar Ahmed <ibrar.ahmad@gmail.com> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
* Doc: update sections 9.5 and 9.6 for new function table layout.Tom Lane2020-04-20
| | | | | | | | Along the way, update the older examples for bytea to use "hex" output format. That lets us get rid of the lame disclaimer about how the examples assume bytea_output = escape, which was only half true anyway because none of the more-recently-added examples had paid any attention to that.
* Doc: update the rest of section 9.4 for new function table layout.Tom Lane2020-04-19
| | | | | Notably, this replaces the previous handwaving about these functions' behavior with "character"-type inputs with some actual facts.
* Doc: update sections 9.1-9.3 for new function table layout.Tom Lane2020-04-19
| | | | | | | | | | | | | | I took the opportunity to do some copy-editing in this area as well, and to add some new material such as a note about BETWEEN's syntactical peculiarities. Of note is that quite a few of the examples of transcendental functions needed to be updated, because the displayed output no longer matched what you get on a modern server. I believe some of these cases are side-effects of the new Ryu algorithm in float8out. Others appear to be because the examples predate the addition of type numeric, and were expecting that float8 calculations would be done although the given syntax would actually lead to calling the numeric function nowadays.
* Doc: sync functableentry markup choices with website style.Tom Lane2020-04-18
| | | | | | | | Jonathan Katz felt that slightly different indentation settings made for a better-looking result, so sync stylesheet-fo.xsl (for PDF) and stylesheet.css (for non-website-style HTML) with those choices. Discussion: https://postgr.es/m/31464.1587156281@sss.pgh.pa.us
* Doc: revise formatting of function/operator tables.Tom Lane2020-04-17
| | | | | | | | | | | | | | | | | | | | | | | The table layout ideas proposed in commit e894c6183 were not as widely popular as I'd hoped. After discussion, we've settled on a layout that's effectively a single-column table with cell contents much like a <varlistentry> description of the function or operator; though we're not actually using <varlistentry>, because it'd add way too much vertical space. Instead the effect is accomplished using line-break processing instructions to separate the description and example(s), plus CSS or FO customizations to produce indentation of all but the first line in each cell. While technically this is a bit grotty, it does have the advantage that we won't need to write nearly as much boilerplate markup. This patch updates tables 9.30, 9.31, and 9.33 (which were touched by the previous patch) to the revised style, and additionally converts table 9.10. A lot of work still remains to do, but hopefully it won't be too controversial. Thanks to Andrew Dunstan, Pierre Giraud, Robert Haas, Alvaro Herrera, David Johnston, Jonathan Katz, Isaac Morland for valuable ideas. Discussion: https://postgr.es/m/8691.1586798003@sss.pgh.pa.us
* Add index term for backup manifest in documentation.Fujii Masao2020-04-17
| | | | | | Author: Fujii Masao Reviewed-by: Robert Haas Discussion: https://postgr.es/m/951743d0-fd7e-8e2b-d489-1368a58b7304@oss.nttdata.com
* Fix the usage of parallel and full options of vacuum command.Amit Kapila2020-04-16
| | | | | | | | | | | | | | | Earlier we were inconsistent in allowing the usage of parallel and full options. Change it such that we disallow them only when they are combined in a way that we don't support. In passing, improve the comments in some of the existing tests of parallel vacuum. Reported-by: Tushar Ahuja Author: Justin Pryzby, Amit Kapila Reviewed-by: Sawada Masahiko, Michael Paquier, Mahendra Singh Thalor and Amit Kapila Discussion: https://postgr.es/m/58c8d171-e665-6fa3-a9d3-d9423b694dae%40enterprisedb.com
* Code review for backup manifest.Fujii Masao2020-04-15
| | | | | | | | | | | | | | | This commit prevents pg_basebackup from receiving backup_manifest file when --no-manifest is specified. Previously, when pg_basebackup was writing a tarfile to stdout, it tried to receive backup_manifest file even when --no-manifest was specified, and reported an error. Also remove unused -m option from pg_basebackup. Also fix typo in BASE_BACKUP command documentation. Author: Fujii Masao Reviewed-by: Michael Paquier, Robert Haas Discussion: https://postgr.es/m/01e3ed3a-8729-5aaa-ca84-e60e3ca59db8@oss.nttdata.com
* Document the backup manifest file format.Robert Haas2020-04-14
| | | | | | | | Patch by me, at the request of Andres Freund. Reviewed by Justin Pryzby, Erik Rijkers, Álvaro Herrera, and Andrew Dunstan. Discussion: http://postgr.es/m/20200327203225.hcm6ag4grwsiruea@alap3.anarazel.de
* Fix collection of typos and grammar mistakes in the tree, volume 2Michael Paquier2020-04-14
| | | | | | | | This fixes some comments and documentation new as of Postgres 13, and is a follow-up of the work done in dd0f37e. Author: Justin Pryzby Discussion: https://postgr.es/m/20200408165653.GF2228@telsasoft.com
* Comments and doc fixes for commit 40d964ec99.Amit Kapila2020-04-14
| | | | | | | Reported-by: Justin Pryzby Author: Justin Pryzby, with few changes by me Reviewed-by: Amit Kapila and Sawada Masahiko Discussion: https://postgr.es/m/20200322021801.GB2563@telsasoft.com
* Silence Perl warningAlvaro Herrera2020-04-13
| | | | | | | | | | Now that warnings are enabled across the board, this code that tries to print an undef variable emits one. Silently printing the empty string achieves the previous behavior. Author: Álvaro Herrera <alvherre@alvh.no-ip.org> Reviewed-by: Andrew Dunstan <andrew.dunstan@2ndquadrant.com> Discussion: https://postgr.es/m/E1jO1VT-0008Qk-TM@gemulon.postgresql.org
* Use perl warnings pragma consistentlyAndrew Dunstan2020-04-13
| | | | | | | | | | We've had a mixture of the warnings pragma, the -w switch on the shebang line, and no warnings at all. This patch removes the -w swicth and add the warnings pragma to all perl sources missing it. It raises the severity of the TestingAndDebugging::RequireUseWarnings perlcritic policy to level 5, so that we catch any future violations. Discussion: https://postgr.es/m/20200412074245.GB623763@rfd.leadboat.com
* Rename pg_validatebackup to pg_verifybackup some more.Robert Haas2020-04-13
| | | | | | | | The previous commit missed an instance. Noriyoshi Shinoda Discussion: http://postgr.es/m/TU4PR8401MB115291AE850BA7CF1AEB2F0BEEDD0@TU4PR8401MB1152.NAMPRD84.PROD.OUTLOOK.COM
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-02 21:56:56 +0000