Release 2024-09-30a #6113
Merged
Release 2024-09-30a #6113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed link error
Added Oracle 21c in a note for database link
* pgd: clarify joining nodes with non-default extensions If a node is joined with a user who does not have superuser permissions, the presence of any extensions on the source node which require superuser permissions to install, will cause the join operation to fail. Clarify that such extensions will need to be created manually on the joining node if the user is not a superuser. BDR-5519. * Apply suggestions from code review --------- Co-authored-by: Dj Walker-Morgan <[email protected]>
…rsion_fix EPAS - Added oracle 21c
Removed "Known Issues" section and altered "Limitations" page title
This summarizes some of the extension-related information spread around the documentation, and also provides something to point at, should end users insist on installing extensions manually, as there is a right way to do it, and a not-so-right way which causes confusion and delay for all concerned. BDR-5141.
Signed-off-by: Dj Walker-Morgan <[email protected]>
Included schema scope options for `-allSchemas` and multiple schemas on Invoking MTK page
…-postgresql-development-environment-setup-windows PostgreSQL on Windows dev env topic
Hi team, Greetings. Hope you are doing well and healthy. When look into this manual page, we found that there is no information about what replaces this feature, despite your letter here suggest to use PEM. (https://knowledge.enterprisedb.com/hc/en-us/articles/15475325526940-End-of-Software-Support-Announcement) So I explicitly added that for users. Kind Regards, Yuki Tei
…6024 Edits to Added note on non-ascii characters not being supported PR6024
Edits to EPRS: fix to offline snapshot steps PR5985
Update 04_pgsnmpd.mdx
…-usage PGD: add documentation section considering extension usage
Signed-off-by: Dj Walker-Morgan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Changed?
#6107 : Adding mergeq tool
#5789 : PGD: add documentation section considering extension usage
#6093 : Update 04_pgsnmpd.mdx
#6078 : Edits to EPRS: fix to offline snapshot steps PR5985
#6090 : Edits to Added note on non-ascii characters not being supported PR6024
#6063 : PostgreSQL on Windows dev env topic
#6032 : Included schema scope options for
-allSchemasand multiple schemas on Invoking MTK page#6100 : Removed "Known Issues" section and altered "Limitations" page title
#6094 : EPAS - Added oracle 21c
#6099 : pgd: clarify joining nodes with non-default extensions