aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* doc PG 17 relnotes: fix "pg_stat_slru_reset" wordingBruce Momjian2024-05-25
| | | | | | | | Reported-by: Marcos Pegoraro Discussion: https://postgr.es/m/CAB-JLwYXrL-8FBfVDX8tevyTJ8y1SMmot5A-5cLqXAAne7W0CQ@mail.gmail.com Backpatch-through: master
* doc PG 17 relnote: adjust "SLRU cache sizes to be configured"Bruce Momjian2024-05-25
| | | | | | | | | | | | Add Álvaro Herrera as additional item author. Reported-by: Álvaro Herrera Discussion: https://postgr.es/m/202405231122.zew2gncy63fo@alvherre.pgsql Author: Álvaro Herrera Backpatch-through: master
* doc PG 17 relnotes: combine itemsBruce Momjian2024-05-25
| | | | | | | | Reported-by: Andres Freund Discussion: https://postgr.es/m/20240524182329.gmzcd3a2zrvyepgy@awork3.anarazel.de Backpatch-through: master
* doc: Clean up title case usePeter Eisentraut2024-05-23
|
* doc: Fix column_name parameter in ALTER MATERIALIZED VIEWMichael Paquier2024-05-23
| | | | | | | | | | Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5-6bd05fc2027e@ewie.name Backpatch-through: 12
* Don't copy extended statistics during MERGE/SPLIT partition operationsAlexander Korotkov2024-05-23
| | | | | | | | | | | | | | | | | | | | When MERGE/SPLIT created new partitions, it was cloning the extended statistics of the parent table. However, extended stats on partitioned tables don't behave like indexes on partitioned tables (which exist only to create physical indexes on child tables). Rather, extended stats on a parent 1) cause extended stats to be collected and computed across the whole partition hierarchy, and 2) do not cause extended stats to be computed for the individual partitions. "CREATE TABLE ... PARTITION OF" command doesn't copy extended statistics. This commit makes createPartitionTable() behave consistently. Reported-by: Justin Pryzby Discussion: https://postgr.es/m/ZiJW1g2nbQs9ekwK%40pryzbyj2023 Author: Alexander Korotkov, Justin Pryzby
* doc PG 17 relnotes: fix pg_stat_reset_shared quotingBruce Momjian2024-05-22
| | | | | | | | Reported-by: torikoshia Discussion: https://postgr.es/m/8ab708436c369d47fcbb23a8ad775ea7@oss.nttdata.com Backpatch-through: master
* doc PG 17 relnotes: fix pg_stat_statements typoBruce Momjian2024-05-22
| | | | | | | | | | Reported-by: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoB_MR=S_Gh=oeJR4ji0GGY+d8747O-5pYcbMbhGOMtAwQ@mail.gmail.com Author: Masahiko Sawada Backpatch-through: master
* doc PG 17 relnotes: adjust SQL/JSON constructor func. authorsBruce Momjian2024-05-22
| | | | | | | | | | Reported-by: Amit Langote Discussion: https://postgr.es/m/CA+HiwqHA2_2V-UtdEEjX3wMUcO=pAwH2D=9P9cRYGVcNLJkH+w@mail.gmail.com Author: Amit Langote Backpatch-through: master
* doc PG 17 relnotes: adjust builtin collation provider itemBruce Momjian2024-05-22
| | | | | | | | Reported-by: Jeff Davis Discussion: https://postgr.es/m/92e039f6fabc3567169e95e12b39a04c00f8503b.camel@j-davis.com Backpatch-through: master
* doc PG 17 relnotes: add Heikki Linnakangas to vacuum itemBruce Momjian2024-05-22
| | | | | | | | | | Reported-by: Melanie Plageman Discussion: https://postgr.es/m/CAAKRu_YYR5MXY-xuCpr7DKKugCExTSjRy9Ax8c-z7LKa8dDfwg@mail.gmail.com Author: Melanie Plageman Backpatch-through: master
* Doc: return 66c0185a3 to the release notes.Robert Haas2024-05-21
| | | | | | | | This reverts commit e1e83a71715f1c2f0717bb66e630ca3bda79b9c1. Per further discussion on pgsql-release, we wish to ship beta1 with that feature, and patch the bug, rather than shipping beta1 with that feature reverted.
* Doc: remove 66c0185a3 from release notes.Tom Lane2024-05-20
| | | | | Discussion: https://postgr.es/m/Zktzf926vslR35Fv@depesz.com (also some private discussion among pgsql-release)
* doc PG 17 relnotes: adjust vacuum itemsBruce Momjian2024-05-20
| | | | | | | | | | Reported-by: John Naylor Discussion: https://postgr.es/m/CANWCAZbPEoFcSjedGsz4AV=_sbwUN4sgjrukVCu-JzrqFC5Hhw@mail.gmail.com Author: John Naylor Backpatch-through: master
* doc PG 17 relnotes: adjust vacuum item to use "or"Bruce Momjian2024-05-19
| | | | | | | | Reported-by: David Rowley Discussion: https://postgr.es/m/CAApHDvrR1ZQ69keUwr5_BGo2iWNqhpZooZSz2g96KnOxO0_GTw@mail.gmail.com Backpatch-through: master
* doc PG 17 relnotes: adjust "builtin" collation providerBruce Momjian2024-05-18
| | | | | | | | Reported-by: Daniel Verite Discussion: https://postgr.es/m/13447ff6-15fd-4137-8339-f4fddda7eb11@manitou-mail.org Backpatch-through: master
* doc PG 17 relnotes: update to currentBruce Momjian2024-05-18
| | | | | | | | Reported-by: jian he Discussion: https://postgr.es/m/CACJufxE7fbWckFeXdW86VTia2BV+LOcfNR-aPf1cP2fjxEB0Aw@mail.gmail.com Backpatch-through: master
* doc PG 17 relnotes: add incremental JSON parser itemBruce Momjian2024-05-18
| | | | | | | | Reported-by: Andrew Dunstan Discussion: https://postgr.es/m/e48dbf1e-62c9-4dbb-8b42-bb9ed898a0ab@dunslane.net Backpatch-through: master
* doc PG 17 relnotes: improve JSON casting itemBruce Momjian2024-05-18
| | | | | | | | Reported-by: jian he Discussion: https://postgr.es/m/CACJufxE0HY19F8Oo-wb-+i4bKDamiaL_aUV8qB69_8mwoScZow@mail.gmail.com Backpatch-through: master
* doc PG 17 relnotes: adjust vacuum memory itemBruce Momjian2024-05-18
| | | | | | | | Reported-by: David Rowley Discussion: https://postgr.es/m/CAApHDvpZnr+wRMX5Wic9Na60fZSbruEffMoECVubBjv483jV2w@mail.gmail.com Backpatch-through: master
* Revise GUC names quoting in messages againPeter Eisentraut2024-05-17
| | | | | | | | | | | | | | | After further review, we want to move in the direction of always quoting GUC names in error messages, rather than the previous (PG16) wildly mixed practice or the intermittent (mid-PG17) idea of doing this depending on how possibly confusing the GUC name is. This commit applies appropriate quotes to (almost?) all mentions of GUC names in error messages. It partially supersedes a243569bf65 and 8d9978a7176, which had moved things a bit in the opposite direction but which then were abandoned in a partial state. Author: Peter Smith <smithpb2250@gmail.com> Discussion: https://www.postgresql.org/message-id/flat/CAHut%2BPv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w%40mail.gmail.com
* Fix documentation about DROP DATABASE FORCE process termination rights.Noah Misch2024-05-16
| | | | | | | | | | | Specifically, it terminates a background worker even if the caller couldn't terminate the background worker with pg_terminate_backend(). Commit 3a9b18b3095366cd0c4305441d426d04572d88c1 neglected to update this. Back-patch to v13, which introduced DROP DATABASE FORCE. Reviewed by Amit Kapila. Reported by Kirill Reshke. Discussion: https://postgr.es/m/20240429212756.60.nmisch@google.com
* Remove option to fall back from direct to postgres SSL negotiationHeikki Linnakangas2024-05-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were three problems with the sslnegotiation options: 1. The sslmode=prefer and sslnegotiation=requiredirect combination was somewhat dangerous, as you might unintentionally fall back to plaintext authentication when connecting to a pre-v17 server. 2. There was an asymmetry between 'postgres' and 'direct' options. 'postgres' meant "try only traditional negotiation", while 'direct' meant "try direct first, and fall back to traditional negotiation if it fails". That was apparent only if you knew that the 'requiredirect' mode also exists. 3. The "require" word in 'requiredirect' suggests that it's somehow more strict or more secure, similar to sslmode. However, I don't consider direct SSL connections to be a security feature. To address these problems: - Only allow sslnegotiation='direct' if sslmode='require' or stronger. And for the record, Jacob and Robert felt that we should do that (or have sslnegotiation='direct' imply sslmode='require') anyway, regardless of the first issue. - Remove the 'direct' mode that falls back to traditional negotiation, and rename what was called 'requiredirect' to 'direct' instead. In other words, there is no "try both methods" option anymore, 'postgres' now means the traditional negotiation and 'direct' means a direct SSL connection. Reviewed-by: Jelte Fennema-Nio, Robert Haas, Jacob Champion Discussion: https://www.postgresql.org/message-id/d3b1608a-a1b6-4eda-9ec5-ddb3e4375808%40iki.fi
* Document that increasing max_connections uses more resources.Robert Haas2024-05-16
| | | | | | Roberto Mello Discussion: http://postgr.es/m/CAKz==bJBCWrvN77fmuZ2XqD3jazWEb=E80AA4Yv9C9tQ61YDdQ@mail.gmail.com
* Doc: use true|false rather than on|off for "failover" optionDavid Rowley2024-05-17
| | | | | | | | | | | | | The CREATE SUBSCRIPTION documentation mentions "false" is the default option, so let's use true|false rather than on|off in the text which talks about this option in the ALTER SUBSCRIPTION page. The other boolean options mentioned in create_subscription.sgml use true and false so it makes sense to be consistent with these. The "failover" option is new to v17. Author: Peter Smith Discussion: https://postgr.es/m/CAHut+Ps-RqrggaJU5w85BbeQzw9CLmmLgADVJoJ=xx_4D5CWvw@mail.gmail.com
* pg_amcheck: Put new options in consistent order in --help and man pagePeter Eisentraut2024-05-16
|
* Revert temporal primary keys and foreign keysPeter Eisentraut2024-05-16
| | | | | | | | | | | | | | | | | | | | This feature set did not handle empty ranges correctly, and it's now too late for PostgreSQL 17 to fix it. The following commits are reverted: 6db4598fcb8 Add stratnum GiST support function 46a0cd4cefb Add temporal PRIMARY KEY and UNIQUE constraints 86232a49a43 Fix comment on gist_stratnum_btree 030e10ff1a3 Rename pg_constraint.conwithoutoverlaps to conperiod a88c800deb6 Use daterange and YMD in without_overlaps tests instead of tsrange. 5577a71fb0c Use half-open interval notation in without_overlaps tests 34768ee3616 Add temporal FOREIGN KEY contraints 482e108cd38 Add test for REPLICA IDENTITY with a temporal key c3db1f30cba doc: clarify PERIOD and WITHOUT OVERLAPS in CREATE TABLE 144c2ce0cc7 Fix ON CONFLICT DO NOTHING/UPDATE for temporal indexes Discussion: https://www.postgresql.org/message-id/d0b64a7a-dfe4-4b84-a906-c7dedfa40a3e@eisentraut.org
* doc PG 17 relnotes: wording adjustmentsBruce Momjian2024-05-15
| | | | | | | | | | Reported-by: jian he Discussion: https://postgr.es/m/CACJufxHTJBqDmBC4iPgte_xd4aMgONRm680Ji5m5gCA8+YEmJg@mail.gmail.com Co-authored-by: jian he Backpatch-through: master
* doc PG 17 relnotes: add item about vacuum storage/limits/WALBruce Momjian2024-05-15
| | | | | | | | Reported-by: Alvaro Herrera Discussion: https://postgr.es/m/202405150838.sg5ddcexyyf4@alvherre.pgsql Backpatch-through: master
* doc: Mention more variant --name=value of -c name=value for postgresMichael Paquier2024-05-16
| | | | | | | | | | | | | | postgres --name=value and -c name=value are equivalents. This commit expands the documentation of libpq's "option" connection parameter and the server startup sequence for shell interactions to mention both rather than only -c. Extracted from a larger patch by the same authors. Reported-by: Alexey Palazhchenko Author: David Johnston, Aleksander Alekseev Reviewed-by: Nathan Bossart, Peter Eisentraut, Álvaro Herrera Discussion: https://postgr.es/m/CAJ7c6TMkuLiLfrA+EFCPYfhXoMKRxxssB5c86+ibxfaz6+=Sdg@mail.gmail.com
* doc: Add standard Environment section to pg_upgrade ref pagePeter Eisentraut2024-05-15
| | | | | Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://www.postgresql.org/message-id/flat/8458c9c5-18f1-46d7-94c4-1c30e4f44908%40eisentraut.org
* doc: Add standard Environment section to pg_amcheck ref pagePeter Eisentraut2024-05-15
| | | | | Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://www.postgresql.org/message-id/flat/8458c9c5-18f1-46d7-94c4-1c30e4f44908%40eisentraut.org
* doc: Remove claims that initdb and pg_ctl use libpq environment variablesPeter Eisentraut2024-05-15
| | | | | | | Erroneously introduced by 571df93cff8. Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://www.postgresql.org/message-id/flat/8458c9c5-18f1-46d7-94c4-1c30e4f44908%40eisentraut.org
* doc PG 17 relnotes: add logical replication apply subtrans itemBruce Momjian2024-05-14
| | | | | | | | Reported-by: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoD5jjB+M+BK5JTis8=W1g8KsS1961FyMqRpj=NBFXrJeA@mail.gmail.com Backpatch-through: master
* doc PG 17 relnotes: remove NOT NULL revert, add ALPN itemBruce Momjian2024-05-14
| | | | | | Make current as of 2024-05-14 Backpatch-through: master
* doc PG 17 relnotes: wording fixBruce Momjian2024-05-14
| | | | | | | | Reported-by: Pantelis Theodosiou Discussion: https://postgr.es/m/CAE3TBxxvkSGJGv7S0SMLSAe0khrQJBHsTca799r=vDJTn+BDAw@mail.gmail.com Backpatch-through: master
* doc PG 17 relnotes: wording fixesBruce Momjian2024-05-14
| | | | | | | | | | Reported-by: Elena Indrupskaya Discussion: https://postgr.es/m/22110133-bca5-4a99-889c-aa0096423456@postgrespro.ru Author: Elena Indrupskaya Backpatch-through: master
* doc PG 17 relnotes: add two optimizer itemsBruce Momjian2024-05-14
| | | | | | | | | | | | | One is about subqueries becoming joins and the other is about optimizing LIMIT by improving startup cost. Reported-by: Andy Fan Discussion: https://postgr.es/m/87h6f4ncc6.fsf@163.com Reviewed-by: David Rowley Backpatch-through: master
* doc PG 17 relnotes: add item about libpq large data transfersBruce Momjian2024-05-13
| | | | | | | | | | Reported-by: Jelte Fennema-Nio Discussion: https://postgr.es/m/CAGECzQTz5aUqLEL6daLd2Hu2FXS_LOSh4keDndJ1fwThsb_b5w@mail.gmail.com Reviewed-by: Joe Conway Backpatch-through: master
* doc PG 17 relnotes: add psql connection control-C itemBruce Momjian2024-05-13
| | | | | | | | | | Reported-by: Jelte Fennema-Nio Discussion: https://postgr.es/m/CAGECzQTz5aUqLEL6daLd2Hu2FXS_LOSh4keDndJ1fwThsb_b5w@mail.gmail.com Reviewed-by: Tom Lane Backpatch-through: master
* Fix pg_sequence_last_value() for unlogged sequences on standbys.Nathan Bossart2024-05-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Presently, when this function is called for an unlogged sequence on a standby server, it will error out with a message like ERROR: could not open file "base/5/16388": No such file or directory Since the pg_sequences system view uses pg_sequence_last_value(), it can error similarly. To fix, modify the function to return NULL for unlogged sequences on standby servers. Since this bug is present on all versions since v15, this approach is preferable to making the ERROR nicer because we need to repair the pg_sequences view without modifying its definition on released versions. For consistency, this commit also modifies the function to return NULL for other sessions' temporary sequences. The pg_sequences view already appropriately filters out such sequences, so there's no bug there, but we might as well offer some defense in case someone invokes this function directly. Unlogged sequences were first introduced in v15, but temporary sequences are much older, so while the fix for unlogged sequences is only back-patched to v15, the temporary sequence portion is back-patched to all supported versions. We could also remove the privilege check in the pg_sequences view definition in v18 if we modify this function to return NULL for sequences for which the current user lacks privileges, but that is left as a future exercise for when v18 development begins. Reviewed-by: Tom Lane, Michael Paquier Discussion: https://postgr.es/m/20240501005730.GA594666%40nathanxps13 Backpatch-through: 12
* Fix typoAlvaro Herrera2024-05-13
|
* Revert structural changes to not-null constraintsAlvaro Herrera2024-05-13
| | | | | | | | | | | | | | | | | | | | | | | | | There are some problems with the new way to handle these constraints that were detected at the last minute, and require fixes that appear too invasive to be doing this late in the cycle. Revert this (again) for now, we'll try again with these problems fixed. The following commits are reverted: b0e96f311985 Catalog not-null constraints 9b581c534186 Disallow changing NO INHERIT status of a not-null constraint d0ec2ddbe088 Fix not-null constraint test ac22a9545ca9 Move privilege check to the right place b0f7dd915bca Check stack depth in new recursive functions 3af721794272 Update information_schema definition for not-null constraints c3709100be73 Fix propagating attnotnull in multiple inheritance d9f686a72ee9 Fix restore of not-null constraints with inheritance d72d32f52d26 Don't try to assign smart names to constraints 0cd711271d42 Better handle indirect constraint drops 13daa33fa5a6 Disallow NO INHERIT not-null constraints on partitioned tables d45597f72fe5 Disallow direct change of NO INHERIT of not-null constraints 21ac38f498b3 Fix inconsistencies in error messages Discussion: https://postgr.es/m/202405110940.joxlqcx4dogd@alvherre.pgsql
* Introduce private data area for injection pointsMichael Paquier2024-05-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit extends the backend-side infrastructure of injection points so as it becomes possible to register some input data when attaching a point. This private data can be registered with the function name and the library name of the callback when attaching a point, then it is given as input argument to the callback. This gives the possibility for modules to pass down custom data at runtime when attaching a point without managing that internally, in a manner consistent with the callback entry retrieved from the hash shmem table storing the injection point data. InjectionPointAttach() gains two arguments, to be able to define the private data contents and its size. A follow-up commit will rely on this infrastructure to close a race condition with the injection point detach in the module injection_points. While on it, this changes InjectionPointDetach() to return a boolean, returning false if a point cannot be detached. This has been mentioned by Noah as useful when it comes to implement more complex tests with concurrent point detach, solid with the automatic detach done for local points in the test module. Documentation is adjusted in consequence. Per discussion with Noah Misch. Reviewed-by: Noah Misch Discussion: https://postgr.es/m/20240509031553.47@rfd.leadboat.com
* Change ALPN protocol ID to IANA-approved "postgresql"Heikki Linnakangas2024-05-11
| | | | | | | | "TBD-pgsql" was a placeholder until the IANA registration was approved. Discussion: https://www.postgresql.org/message-id/87jzk2hj2n.fsf%40wibble.ilmari.org Discussion: https://mailarchive.ietf.org/arch/msg/tls-reg-review/9LWPzQfOpbc8dTT7vc9ahNeNaiw/
* doc PG 17 relnotes: move FETCH_COUNT item, and clarifyBruce Momjian2024-05-10
| | | | Backpatch-through: master
* doc PG 17 relnotes: add FETCH_COUNT itemBruce Momjian2024-05-10
| | | | | | | | Reported-by: Daniel Verite Discussion: https://postgr.es/m/82569de4-9b2a-4311-beb2-81d5418491ec@manitou-mail.org Backpatch-through: master
* Doc: update the "Using EXPLAIN" examples to match current code.Tom Lane2024-05-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | A lot of the examples in this section are quite ancient and no longer match the system's current behavior. I ran through them and updated the sample output to match what I get today. Notably, it seems that the tenk1 table got a few pages smaller back around v12, so that a lot of the cost estimates for queries on that table are a little different now. (This also caused some examples to surprisingly not match others, depending on when they were made.) One mergejoin-based example no longer produces the same plan at all, so I had to work around that, including switching to a different example of using an enable_xxx setting. I also changed a couple of examples that were relying on nonexistent tables or indexes. IMO the premise of this section is that the examples should be more-or-less reproducible against the regression database, so that these examples were unhelpful as given. It's not that hard to find a corresponding example with the tables we do have. Some of the EXPLAIN ANALYZE examples were out of date in that we show more numbers than we did at the time. Possibly chapter 68 could use similar review, but I'm out of energy for today.
* doc PG 17 relnotes: fix author of LLVM itemBruce Momjian2024-05-09
| | | | | | Discussion: https://postgr.es/m/CA+hUKG+yU4+YqsCuQuzdCeETPdU+FjebXgV5Fkp6xrtr7EKC3w@mail.gmail.com Backpatch-through: master
* doc: clarify PERIOD and WITHOUT OVERLAPS in CREATE TABLEBruce Momjian2024-05-09
| | | | | | | | Discussion: https://postgr.es/m/04938501-fc8f-46f3-97a4-9a81a3f24530@illuminatedcomputing.com Author: Paul Jungwirth Backpatch-through: master
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 00:58:31 +0000