summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
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
2017-04-18Fix example on creating a trigger with a transition table.Heikki Linnakangas
Yugo Nagata Discussion: https://www.postgresql.org/message-id/20170417180921.3047f3b0.nagata@sraoss.co.jp
2017-04-17doc: Clarify logical replication detailsPeter Eisentraut
Document more explicitly that the target table can have more columns than the source table. Reported-by: Euler Taveira <euler@timbira.com.br>
2017-04-17Rename columns in new pg_statistic_ext catalogAlvaro Herrera
The new catalog reused a column prefix "sta" from pg_statistic, but this is undesirable, so change the catalog to use prefix "stx" instead. Also, rename the column that lists enabled statistic kinds as "stxkind" rather than "enabled". Discussion: https://postgr.es/m/CAKJS1f_2t5jhSN7huYRFH3w3rrHfG2QU7hiUHsu-Vdjd1rYT3w@mail.gmail.com
2017-04-17Tighten up relation kind checks for extended statisticsAlvaro Herrera
We were accepting creation of extended statistics only for regular tables, but they can usefully be created for foreign tables, partitioned tables, and materialized views, too. Allow those cases. While at it, make sure all the rejected cases throw a consistent error message, and add regression tests for the whole thing. Author: David Rowley, Álvaro Herrera Discussion: https://postgr.es/m/CAKJS1f-BmGo410bh5RSPZUvOO0LhmHL2NYmdrC_Jm8pk_FfyCA@mail.gmail.com
2017-04-17Document that ONLY can be specified in publication commandsPeter Eisentraut
Author: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
2017-04-14doc: Fix typoPeter Eisentraut
2017-04-14Fix typo in commentPeter Eisentraut
2017-04-14Add option to modify sync commit per subscriptionPeter Eisentraut
This also changes default behaviour of subscription workers to synchronous_commit = off. Author: Petr Jelinek <petr.jelinek@2ndquadrant.com>
2017-04-13doc: add missing sect1 close tagBruce Momjian
Fixes commit 4f3b87ab780b95c2cc8a591259baefaff4852037
2017-04-13Improve the SASL authentication protocol.Heikki Linnakangas
This contains some protocol changes to SASL authentiation (which is new in v10): * For future-proofing, in the AuthenticationSASL message that begins SASL authentication, provide a list of SASL mechanisms that the server supports, for the client to choose from. Currently, it's always just SCRAM-SHA-256. * Add a separate authentication message type for the final server->client SASL message, which the client doesn't need to respond to. This makes it unambiguous whether the client is supposed to send a response or not. The SASL mechanism should know that anyway, but better to be explicit. Also, in the server, support clients that don't send an Initial Client response in the first SASLInitialResponse message. The server is supposed to first send an empty request in that case, to which the client will respond with the data that usually comes in the Initial Client Response. libpq uses the Initial Client Response field and doesn't need this, and I would assume any other sensible implementation to use Initial Client Response, too, but let's follow the SASL spec. Improve the documentation on SASL authentication in protocol. Add a section describing the SASL message flow, and some details on our SCRAM-SHA-256 implementation. Document the different kinds of PasswordMessages that the frontend sends in different phases of SASL authentication, as well as GSS/SSPI authentication as separate message formats. Even though they're all 'p' messages, and the exact format depends on the context, describing them as separate message formats makes the documentation more clear. Reviewed by Michael Paquier and Álvaro Hernández Tortosa. Discussion: https://www.postgresql.org/message-id/CAB7nPqS-aFg0iM3AQOJwKDv_0WkAedRjs1W2X8EixSz+sKBXCQ@mail.gmail.com
2017-04-13pg_dump: Always dump subscriptions NOCONNECTPeter Eisentraut
This removes the pg_dump option --no-subscription-connect and makes it the default. Dumping a subscription so that it activates right away when restored is not very useful, because the state of the publication server is unclear. Discussion: https://www.postgresql.org/message-id/e4fbfad5-c6ac-fd50-6777-18c84b34eb2f@2ndquadrant.com
2017-04-13pg_dump: Dump subscriptions by defaultPeter Eisentraut
Dump subscriptions if the current user is a superuser, otherwise write a warning and skip them. Remove the pg_dump option --include-subscriptions. Discussion: https://www.postgresql.org/message-id/e4fbfad5-c6ac-fd50-6777-18c84b34eb2f@2ndquadrant.com
2017-04-13Fix XMLTABLE synopsis, add XMLNAMESPACES exampleAlvaro Herrera
Add a missing comma in the synopsis after the XMLNAMESPACES clause. Also, add an example illustrating the use of that clause. Author: Arjen Nienhuis and Pavel Stěhule
2017-04-13Remove pg_stats_ext viewAlvaro Herrera
It was created as equivalent of pg_stats, but since the code underlying pg_statistic_ext is more convenient than the one for pg_statistic, pg_stats_ext is no longer useful. Author: David Rowley Reviewed-by: Tomas Vondra Discussion: https://postgr.es/m/CAKJS1f9zAkPUf9nQrqpFBAsrOHvb5eYa2FVNsmCJy1wegcO_TQ@mail.gmail.com
2017-04-13Move pg_stat_progress_vacuum to the table of Dynamic Statistics Views in doc.Fujii Masao
Previously the description about pg_stat_progress_vacuum was in the table of "Collected Statistics Views" in the doc. But since it repors dynamic information, i.e., the current progress of VACUUM, its description should be in the table of "Dynamic Statistics Views". Back-patch to 9.6 where pg_stat_progress_vacuum was added. Author: Amit Langote Discussion: http://postgr.es/m/7ab51b59-8d4d-6193-c60a-b75f222efb12@lab.ntt.co.jp
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-30 04:22:16 +0000