aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* doc: Add links to tablesPeter Eisentraut2019-06-05
| | | | | Formal tables should generally have an xref in the text that points to them. Add them here.
* Document piecemeal construction of partitioned indexesAlvaro Herrera2019-06-04
| | | | | | | | | Continuous operation cannot be achieved without applying this technique, so it needs to be properly described. Author: Álvaro Herrera Reported-by: Tom Lane Discussion: https://postgr.es/m/8756.1556302759@sss.pgh.pa.us
* doc: Fix whitespacePeter Eisentraut2019-06-04
| | | | Verbatim environment tags should not be indented.
* Add command column to pg_stat_progress_create_indexPeter Eisentraut2019-06-04
| | | | | | | This allows determining which command is running, similar to pg_stat_progress_cluster. Discussion: https://www.postgresql.org/message-id/flat/f0e56b3b-74b7-6cbc-e207-a5ed6bee18dc%402ndquadrant.com
* Fix documentation of check_option in information_schema.viewsMichael Paquier2019-06-01
| | | | | | | | | | Support of CHECK OPTION for updatable views has been added in 9.4, but the documentation of information_schema never got the call even if the information displayed is correct. Author: Gilles Darold Discussion: https://postgr.es/m/75d07704-6c74-4f26-656a-10045c01a17e@darold.net Backpatch-through: 9.4
* Rework options of pg_checksums options for filenode handlingMichael Paquier2019-05-30
| | | | | | | | | | This makes the tool consistent with the option set of oid2name, which has been historically using -f for filenodes, and has more recently gained long options and --filenode via 1aaf532. Reported-by: Peter Eisentraut Author: Fabien Coelho Discussion: https://postgr.es/m/97045260-fb9e-e145-a950-cf7d28c4eaea@2ndquadrant.com
* Fix some documentation about access methodsMichael Paquier2019-05-29
| | | | | Author: Guillaume Lelarge Discussion: https://postgr.es/m/CAECtzeWPz4JikzUqZdMjqPTe8dAP3nZxPD-58Y-Hhvirg0fF+A@mail.gmail.com
* Fix some documentation about FKs and partitioned tablesMichael Paquier2019-05-29
| | | | | | | | | | This got forgotten in f56f8f which has added foreign key support for partitioned tables. In passing, add a mention about caveats applying to tables partitioned using inheritance regarding indexes and foreign keys. Author: Paul A Jungwirth Reviewed-by: Amit Langote, Michael Paquier Discussion: https://postgr.es/m/CA+renyUuSmYgmZjKc_DfUNVZ0uttF91-FwhDVW3F7WEPj0jL5w@mail.gmail.com
* v12 release notes: Correct contributor name.Andres Freund2019-05-28
| | | | Mea culpa.
* docs: PG 12 relnote wording fixBruce Momjian2019-05-28
| | | | Reported-by: Gaby Schilders
* doc: Fix generated column documentationPeter Eisentraut2019-05-27
| | | | | | | The old text still had an implicit reference to the virtual behavior, which was not in the final patch. Author: Tobias Bussmann <t.bussmann@gmx.net>
* Fix typos.Amit Kapila2019-05-26
| | | | | | | Reported-by: Alexander Lakhin Author: Alexander Lakhin Reviewed-by: Amit Kapila and Tom Lane Discussion: https://postgr.es/m/7208de98-add8-8537-91c0-f8b089e2928c@gmail.com
* Change Graphviz file extensionPeter Eisentraut2019-05-26
| | | | | | | Change extension for Graphviz files from .dot to .gv. The latter appears to be the generally preferred one nowadays. Discussion: https://www.postgresql.org/message-id/flat/71fe76d2-c7d7-2acc-6762-bbf9e61c566e%402ndquadrant.com
* Doc: fix incorrect references in PG 12 release notes.Amit Kapila2019-05-25
| | | | | | Reported-by: Euler Taveira Author: Euler Taveira Discussion: https://postgr.es/m/CAHE3wgjiA8DdnUzH9WqBLxdrUVvjDkKNdHx-MkEg9uV+HtpMfg@mail.gmail.com
* Doc: fix typo in pgbench random_zipfian() documentation.Tom Lane2019-05-24
| | | | | | Per bug #15819 from Koizumi Satoru. Discussion: https://postgr.es/m/15819-e6191bef1f7334c0@postgresql.org
* Remove -o/--oids from pg_dumpallMichael Paquier2019-05-23
| | | | | | | | This has been forgotten in 578b229, which has removed support for WITH OIDS. Discussion: https://postgr.es/m/CALAY4q99FcFCoG6ddke0V-AksGe82L_+bhDWgEfgZBakB840zA@mail.gmail.com Author: Surafel Temesgen
* Mention ANALYZE boolean options in documentation.Fujii Masao2019-05-23
| | | | | | | | | | | | | | Commit 41b54ba78e allowed not only VACUUM but also ANALYZE options to take a boolean argument. But it forgot to update the documentation for ANALYZE. This commit adds the descriptions about those ANALYZE boolean options into the documentation. This patch also updates tab-completion for ANALYZE boolean options. Reported-by: Kyotaro Horiguchi Author: Fujii Masao Reviewed-by: Masahiko Sawada, Michael Paquier Discussion: https://postgr.es/m/CAHGQGwHTUt-kuwgiwe8f0AvTnB+ySqJWh95jvmh-qcoKW9YA9g@mail.gmail.com
* docs: PG 12 release notes, support functionsBruce Momjian2019-05-22
| | | | | | | | Move support function mention to the proper section, and reword. Reported-by: Tom Lane Discussion: https://postgr.es/m/5121.1558472431@sss.pgh.pa.us
* doc: PG 12 relnotes, correct recovery_target* variable mentionBruce Momjian2019-05-22
| | | | | | | | Clarify new restriction on recovery_target* variables. Reported-by: Gaby Schilders Discussion: reported via chat
* docs: PG 12 relnote adjustments based on feedback from Tom LaneBruce Momjian2019-05-21
| | | | Discussion: https://postgr.es/m/22793.1558399695@sss.pgh.pa.us
* docs: adjust RECORD PG 12 relnote itemBruce Momjian2019-05-21
| | | | Discussion: https://postgr.es/m/15486.1558393010@sss.pgh.pa.us
* doc: adjust PG 12 relnotes item on float digit adjustmentBruce Momjian2019-05-21
| | | | Discussion: https://postgr.es/m/87y330d8ty.fsf@news-spur.riddles.org.uk
* doc: fix markup for PG 12 rel notesBruce Momjian2019-05-21
|
* doc: adjustments for PG 12 release notesBruce Momjian2019-05-21
| | | | | | | Mostly commit messages, attribution, and text, all suggested by Andres Freund. Discussion: https://postgr.es/m/20190520221719.pqgld3krjc2docr5@alap3.anarazel.de
* Doc: improve description of regexp character classes.Tom Lane2019-05-20
| | | | | | | | | | | | | | | | Define the meanings of the POSIX-spec character classes in line, rather than referring to the ctype(3) man page. That man page doesn't even exist on many modern systems, and if it does exist it probably says the wrong things about non-ASCII characters. Also document our non-POSIX-spec "ascii" character class. Also, point out here that this behavior is controlled by collation or LC_CTYPE, since the existing text explaining that is pretty far away. Per gripe from Geert Lobbestael. Given the lack of prior complaints, I'm not excited about back-patching this. Discussion: https://postgr.es/m/155837022049.1359.2948065118562813468@wrigleys.postgresql.org
* Fix some grammar in documentation of spgist and pgbenchMichael Paquier2019-05-20
| | | | | | | Discussion: https://postgr.es/m/92961161-9b49-e42f-0a72-d5d47e0ed4de@postgrespro.ru Author: Liudmila Mantrova Reviewed-by: Jonathan Katz, Tom Lane, Michael Paquier Backpatch-through: 9.4
* Improve documentation for array subscription in jsonpathAlexander Korotkov2019-05-19
| | | | | Usage of expressions and multiple ranges in jsonpath array subscription was undocumented. This commit adds lacking documentation.
* Document jsonpath .** accessor with nesting level filterAlexander Korotkov2019-05-19
| | | | | | | | | | | It appears that some variants of .** jsonpath accessor are undocumented. In particular undocumented variants are: .**{level} .**{lower_level to upper_level} .**{lower_level to last} This commit adds missing documentation for them.
* docs: tighten up PG 12 release note item on 1k partitionsBruce Momjian2019-05-18
|
* docs: split out sort-skip partition item in PG 12 release notesBruce Momjian2019-05-17
| | | | Discussion: https://postgr.es/m/0cf10a27-c6a0-de4a-cd20-ab7493ea7422@lab.ntt.co.jp
* Fix typos in documentatoin of GSSAPI encryptionMichael Paquier2019-05-17
| | | | | Author: Daniel Gustafsson Discussion: https://postgr.es/m/5520EDD8-7AC7-4307-8171-400DD1D84FDC@yesql.se
* docs: properly indent PG 12 release notesBruce Momjian2019-05-15
|
* docs: Indent listitem tags in PG 12 release notesBruce Momjian2019-05-14
|
* Fix SQL-style substring() to have spec-compliant greediness behavior.Tom Lane2019-05-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SQL's regular-expression substring() function is defined to have a pattern argument that's separated into three subpatterns by escape- double-quote markers; the function result is the part of the input matching the second subpattern. The standard makes it clear that if there is ambiguity about how to match the input to the subpatterns, the first and third subpatterns should be taken to match the smallest possible amount of text (i.e., they're "non greedy", in the terms of our regex code). We were not doing it that way: the first subpattern would eat the largest possible amount of text, causing the function result to be shorter than what the spec requires. Fix that by attaching explicit greediness quantifiers to the subpatterns. (This depends on the regex fix in commit 8a29ed053; before that, this didn't reliably change the regex engine's behavior.) Also, by adding parentheses around each subpattern, we ensure that "|" (OR) in the subpatterns behave sanely. Previously, "|" in the first or third subpatterns didn't work. This patch also makes the function throw error if you write more than two escape-double-quote markers, and do something sane if you write just one, and document that behavior. Previously, an odd number of markers led to a confusing complaint about unbalanced parentheses, while extra pairs of markers were just ignored. (Note that the spec requires exactly two markers, but we've historically allowed there to be none, and this patch preserves the old behavior for that case.) In passing, adjust some substring() test cases that didn't really prove what they said they were testing for: they used patterns that didn't match the data string, so that the output would be NULL whether or not the function was really strict. Although this is certainly a bug fix, changing the behavior in back branches seems undesirable: applications could perhaps be depending on the old behavior, since it's not obviously wrong unless you read the spec very closely. Hence, no back-patch. Discussion: https://postgr.es/m/5bb27a41-350d-37bf-901e-9d26f5592dd0@charter.net
* Update SQL features/conformance information to SQL:2016Peter Eisentraut2019-05-14
|
* Update SQL keywords list to SQL:2016Peter Eisentraut2019-05-14
| | | | | | | | | | | | | | Per previous convention (see ace397e9d24eddc56e7dffa921f506117b602d78), drop SQL:2008 and only keep the latest two standards and SQL-92. Note: SQL:2016-2 lists a large number of non-reserved keywords that are really just information_schema column names related to new features. Those kinds of thing have not previously been listed as keywords, and this was apparently done here by mistake, since these keywords have been removed again in post-2016 working drafts. So in order to avoid bloating the keywords table unnecessarily, I have omitted these erroneous keywords here.
* docs: update partition item in PG 12 release notesBruce Momjian2019-05-14
| | | | | | Reported-by: Amit Langote Discussion: https://postgr.es/m/b7954643-41ef-a174-479d-1f8d4834f40a@lab.ntt.co.jp
* docs: fix duplicate wording in PG 12 release notesBruce Momjian2019-05-14
| | | | | | Reported-by: nickb@imap.cc Discussion: https://postgr.es/m/6b3414e1-fcef-4ad9-b123-b3ab3702d3db@www.fastmail.com
* doc: Update OID item in PG 12 release notesBruce Momjian2019-05-13
| | | | | | Reported-by: Justin Pryzby Discussion: https://postgr.es/m/20190513174759.GE23251@telsasoft.com
* doc: improve wording of PG 12 releaase note partition itemBruce Momjian2019-05-13
| | | | | | Reported-by: Amit Langote Discussion: https://postgr.es/m/d5267ae5-bd4a-3e96-c21b-56bfa9fec7e8@lab.ntt.co.jp
* doc: properly attibute PG 12 pgbench release note itemBruce Momjian2019-05-13
| | | | | | Reported-by: Fabien COELHO Discussion: https://postgr.es/m/alpine.DEB.2.21.1905130839140.13487@lancre
* Doc: Refer to line pointers as item identifiers.Peter Geoghegan2019-05-13
| | | | | | | | | | | An upcoming HEAD-only patch will standardize the terminology around ItemIdData variables/line pointers, ending the practice of referring to them as "item pointers". Make the "Database Page Layout" docs consistent with the new policy. The term "item identifier" is already used in the same section, so stick with that. Discussion: https://postgr.es/m/CAH2-Wz=c=MZQjUzde3o9+2PLAPuHTpVZPPdYxN=E4ndQ2--8ew@mail.gmail.com Backpatch: All supported branches.
* doc: PG 12 release notes: normalize attribution namesBruce Momjian2019-05-12
| | | | | | Reported-by: David Rowley Discussion: https://postgr.es/m/CAKJS1f-ktEhmQ2zJQ1L1niuJ9KB8WPA-bE-AhGiFsSO6QASB_w@mail.gmail.com
* doc: adjust PG 12 release note sectionsBruce Momjian2019-05-12
| | | | Tighten section designations.
* docs: fix typo in mention of MSVCBruce Momjian2019-05-12
|
* docs: remove second mention of btree max length reductionBruce Momjian2019-05-11
| | | | | | I already added that to the incompatibility section as a separate item. Reported-by: Peter Geoghegan
* doc: remove pg_config mention from PG 12 release notesBruce Momjian2019-05-11
| | | | | | Reported-by: Tom Lane Discussion: https://postgr.es/m/28209.1556556696@sss.pgh.pa.us
* docs: PG 12 release notes, mention that REINDEX could now failBruce Momjian2019-05-11
| | | | | | This is because of the new tid in the index entry. Reported-by: Peter Geoghegan
* docs: add links from the PG 12 release notes to the main docsBruce Momjian2019-05-11
|
* docs: adjust PG 12 floating point itemBruce Momjian2019-05-11
| | | | | | Reported-by: Andrew Gierth Discussion: https://postgr.es/m/87r295hjur.fsf@news-spur.riddles.org.uk
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-22 14:35:53 +0000