summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2017-05-06Document current_role.Tom Lane
This system function has been there a very long time, but somehow escaped being listed in func.sgml. Fabien Coelho and Tom Lane Discussion: https://postgr.es/m/alpine.DEB.2.20.1705061027580.3896@lancre
2017-05-05First-draft release notes for 9.6.3.Tom Lane
As usual, the release notes for other branches will be made by cutting these down, but put them up for community review first. Note there are some entries that really only apply to pre-9.6 branches.
2017-05-05Prevent panic during shutdown checkpointPeter Eisentraut
When the checkpointer writes the shutdown checkpoint, it checks afterwards whether any WAL has been written since it started and throws a PANIC if so. At that point, only walsenders are still active, so one might think this could not happen, but walsenders can also generate WAL, for instance in BASE_BACKUP and certain variants of CREATE_REPLICATION_SLOT. So they can trigger this panic if such a command is run while the shutdown checkpoint is being written. To fix this, divide the walsender shutdown into two phases. First, the postmaster sends a SIGUSR2 signal to all walsenders. The walsenders then put themselves into the "stopping" state. In this state, they reject any new commands. (For simplicity, we reject all new commands, so that in the future we do not have to track meticulously which commands might generate WAL.) The checkpointer waits for all walsenders to reach this state before proceeding with the shutdown checkpoint. After the shutdown checkpoint is done, the postmaster sends SIGINT (previously unused) to the walsenders. This triggers the existing shutdown behavior of sending out the shutdown checkpoint record and then terminating. Author: Michael Paquier <michael.paquier@gmail.com> Reported-by: Fujii Masao <masao.fujii@gmail.com>
2017-05-04doc: update PG 10 release notesBruce Momjian
Mention vacuum verbose includes oldest xmin, BRIN index usage estimation, and multi-column statistics. Reported-by: Masahiko Sawada, Alvaro Herrera
2017-05-04doc: PG 10 release note updates for psql, GiST, and markupBruce Momjian
Reported-by: Andrew Borodin, Fabien COELHO, Dagfinn Ilmari Mannsaker
2017-05-04Credit Claudio as main author of featureAlvaro Herrera
2017-05-04Fix PQencryptPasswordConn to work with older server versions.Heikki Linnakangas
password_encryption was a boolean before version 10, so cope with "on" and "off". Also, change the behavior with "plain", to treat it the same as "md5". We're discussing removing the password_encryption='plain' option from the server altogether, which will make this the only reasonable choice, but even if we kept it, it seems best to never send the password in cleartext.
2017-05-03Add PQencryptPasswordConn function to libpq, use it in psql and createuser.Heikki Linnakangas
The new function supports creating SCRAM verifiers, in addition to md5 hashes. The algorithm is chosen based on password_encryption, by default. This fixes the issue reported by Jeff Janes, that there was previously no way to create a SCRAM verifier with "\password". Michael Paquier and me Discussion: https://www.postgresql.org/message-id/CAMkU%3D1wfBgFPbfAMYZQE78p%3DVhZX7nN86aWkp0QcCp%3D%2BKxZ%3Dbg%40mail.gmail.com
2017-05-02extstats: change output functions to emit valid JSONAlvaro Herrera
Manipulating extended statistics is more convenient as JSON than the current ad-hoc format, so let's change before it's too late. Discussion: https://postgr.es/m/20170420193828.k3fliiock5hdnehn@alvherre.pgsql
2017-05-02doc: Improve order in ALTER PUBLICATION/SUBSCRIPTION ref pagesPeter Eisentraut
Move the OWNER and RENAME clauses to the end, so the interesting functionality is listed first. This is more typical on nearby reference pages, whereas the previous order was the order in which the clauses were added.
2017-05-02doc: Add missing markupPeter Eisentraut
2017-05-02doc: Update ALTER SEQUENCE claims about changes being nontransactionalPeter Eisentraut
Clarify that all changes except RESTART are transactional (since 1753b1b027035029c2a2a1649065762fafbf63f3). Reported-by: Michael Paquier <michael.paquier@gmail.com>
2017-05-02Change hot_standby default value to 'on'Magnus Hagander
This goes together with the changes made to enable replication on the sending side by default (wal_level, max_wal_senders etc) by making the receiving stadby node also enable it by default. Huong Dangminh
2017-05-01Fire per-statement triggers on partitioned tables.Robert Haas
Even though no actual tuples are ever inserted into a partitioned table (the actual tuples are in the partitions, not the partitioned table itself), we still need to have a ResultRelInfo for the partitioned table, or per-statement triggers won't get fired. Amit Langote, per a report from Rajkumar Raghuwanshi. Reviewed by me. Discussion: http://postgr.es/m/CAKcux6%3DwYospCRY2J4XEFuVy0L41S%3Dfic7rmkbsU-GXhhSbmBg%40mail.gmail.com
2017-04-28doc: Fix typo in 9.6 release notesPeter Eisentraut
Author: Huong Dangminh <huo-dangminh@ys.jp.nec.com>
2017-04-27Remove unnecessairly duplicated gram.y productionsStephen Frost
Declarative partitioning duplicated the TypedTableElement productions, evidently to remove the need to specify WITH OPTIONS when creating partitions. Instead, simply make WITH OPTIONS optional in the TypedTableElement production and remove all of the duplicate PartitionElement-related productions. This change simplifies the syntax and makes WITH OPTIONS optional when adding defaults, constraints or storage parameters to columns when creating either typed tables or partitions. Also update pg_dump to no longer include WITH OPTIONS, since it's not necessary, and update the documentation to reflect that WITH OPTIONS is now optional.
2017-04-27doc: PG10 release note typo fixBruce Momjian
Reported-by: daniel.westermann
2017-04-27doc PG10rel: adjust hash index commits and add parallel subqueryBruce Momjian
Reported-by: Amit Kapila
2017-04-26doc PG10: add commit for transition table itemBruce Momjian
2017-04-26doc: ALTER SUBSCRIPTION documentation fixesPeter Eisentraut
WITH is optional for REFRESH PUBLICATION. Also, remove a spurious bracket and fix a punctuation. Author: Euler Taveira <euler@timbira.com.br>
2017-04-26doc PG10: add Rafia Sabih to parallel index scan itemBruce Momjian
Reported-by: Amit Kapila
2017-04-25Allow ALTER TABLE ONLY on partitioned tablesStephen Frost
There is no need to forbid ALTER TABLE ONLY on partitioned tables, when no partitions exist yet. This can be handy for users who are building up their partitioned table independently and will create actual partitions later. In addition, this is how pg_dump likes to operate in certain instances. Author: Amit Langote, with some error message word-smithing by me
2017-04-25doc PG10: update EXPLAIN SUMMARY itemBruce Momjian
Reported-by: Tels
2017-04-25doc: update PG 10 item about referencing many relationsBruce Momjian
Reported-by: Tom Lane
2017-04-25doc: add PG 10 doc item about VACUUM truncation, 7e26e02eeBruce Momjian
Reported-by: Andres Freund
2017-04-25doc PG10: add commit 090010f2e and adjust EXPLAIN SUMMARY itemBruce Momjian
Reported-by: Tels, Andres Freund
2017-04-25doc: properly indent SGML tags in PG 10 release notesBruce Momjian
2017-04-25doc: PG 10 release notes updatesBruce Momjian
Reported-by: Michael Paquier, Felix Gerzaguet
2017-04-25doc: PG 10 release note updatesBruce Momjian
Reported-by: David Rowley, Amit Langote, Ashutosh Bapat
2017-04-25doc: move hash info to new section and split out growth itemBruce Momjian
Reported-by: Amit Kapila
2017-04-24doc: move hash performance item into index sectionBruce Momjian
The requirement to rebuild pg_upgrade-ed hash indexes was kept in the incompatibilities section. Reported-by: Amit Kapila
2017-04-24doc: add Rafia Sabih to PG 10 release note itemBruce Momjian
Reported-by: Amit Kapila
2017-04-24doc: fix PG 10 release note doc markupBruce Momjian
2017-04-24doc: merge PG 10 release SysV itemBruce Momjian
Reported-by: Takayuki Tsunakawa
2017-04-24doc: PG 10 fixesBruce Momjian
Reported-by: Takayuki Tsunakawa
2017-04-24doc: several minor PG 10 doc adjustmentsBruce Momjian
2017-04-24doc: fix attribution of sequence item, order incompatibilitiesBruce Momjian
Reported-by: Andreas Karlsson
2017-04-24doc: first draft of Postgres 10 release notesBruce Momjian
2017-04-24doc: update release doc markup instructionsBruce Momjian
2017-04-21doc: Update linkPeter Eisentraut
The reference "That is the topic of the next section." has been incorrect since the materialized views documentation got inserted between the section "rules-views" and "rules-update". Author: Zertrin <postgres_wiki@zertrin.org>
2017-04-21Change the on-disk format of SCRAM verifiers to conform to RFC 5803.Heikki Linnakangas
It doesn't make any immediate difference to PostgreSQL, but might as well follow the standard, since one exists. (I looked at RFC 5803 earlier, but didn't fully understand it back then.) The new format uses Base64 instead of hex to encode StoredKey and ServerKey, which makes the verifiers slightly smaller. Using the same encoding for the salt and the keys also means that you only need one encoder/decoder instead of two. Although we have code in the backend to do both, we are talking about teaching libpq how to create SCRAM verifiers for PQencodePassword(), and libpq doesn't currently have any code for hex encoding. Bump catversion, because this renders any existing SCRAM verifiers in pg_authid invalid. Discussion: https://www.postgresql.org/message-id/351ba574-85ea-d9b8-9689-8c928dd0955d@iki.fi
2017-04-21doc: Fix typoPeter Eisentraut
2017-04-20Improve multivariate statistics documentationAlvaro Herrera
Extended statistics commit 7b504eb282c did not include appropriate documentation next to where we document regular planner statistics (I ripped what was submitted before commit and then forgot to put it back), and while later commit 2686ee1b7ccf added some material, it structurally depended on what I had ripped out, so the end result wasn't proper. Fix those problems by shuffling what was added by 2686ee1b7ccf and including some additional material, so that now chapter 14 "Performance Tips" now describes the types of multivariate statistics we currently have, and chapter 68 "How the Planner Uses Statistics" shows some examples. The new text should be more in line with previous material, in (hopefully) the appropriate depth. While at it, fix a small bug in pg_statistic_ext docs: one column was listed in the wrong spot.
2017-04-20Sync pg_ctl documentation and usage message with reality.Tom Lane
Commit 05cd12ed5 ("pg_ctl: Change default to wait for all actions") was a tad sloppy about updating the documentation to match. The documentation was also sorely in need of a copy-editing pass, having been adjusted at different times by different people who took little care to maintain consistency of style.
2017-04-20Modify message when partitioned table is added to publicationPeter Eisentraut
Give a more specific error message than "xyz is not a table". Also document in CREATE PUBLICATION which kinds of relations are not supported. based on patch by Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
2017-04-19Fix typo in docs on SASL authentication.Heikki Linnakangas
Word "sends" was missing. Jaime Casanova
2017-04-18Doc: improve markup in self-signed certificate example.Tom Lane
2017-04-19Improve documentation and comment for quorum-based sync replication.Fujii Masao
Author: Masahiko Sawada, heavily modified by me Discussion: http://postgr.es/m/CAHGQGwEKOw=SmPLxJzkBsH6wwDBgOnVz46QjHbtsiZ-d-2RGUg@mail.gmail.com
2017-04-18Simplify docs on creating a self-signed SSL certificateAndrew Dunstan
Discussion: <https://postgr.es/m/72335afb-969b-af84-3fcb-1739e3ed09a6@2ndQuadrant.com>
2017-04-18Rename "scram" to "scram-sha-256" in pg_hba.conf and password_encryption.Heikki Linnakangas
Per discussion, plain "scram" is confusing because we actually implement SCRAM-SHA-256 rather than the original SCRAM that uses SHA-1 as the hash algorithm. If we add support for SCRAM-SHA-512 or some other mechanism in the SCRAM family in the future, that would become even more confusing. Most of the internal files and functions still use just "scram" as a shorthand for SCRMA-SHA-256, but I did change PASSWORD_TYPE_SCRAM to PASSWORD_TYPE_SCRAM_SHA_256, as that could potentially be used by 3rd party extensions that hook into the password-check hook. Michael Paquier did this in an earlier version of the SCRAM patch set already, but I didn't include that in the version that was committed. Discussion: https://www.postgresql.org/message-id/fde71ff1-5858-90c8-99a9-1c2427e7bafb@iki.fi
generated by cgit v1.2.3 (git 2.46.0) at 2025-11-07 21:18:52 +0000