docs: clarify demo control files and shared WAL modes - #84
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documentation-only continuation of the four-Pod installation manual. Distinguishes per-instance ownership from shared physical storage, shows optional control-file symlinks and per-thread WAL layout, and states the actual demo defaults and recovery limits. Adds read-only SHOW checks and Oracle primary references. No product, deployment configuration, workflow, or image-publication changes. The existing image publication hold remains in force. Local verification: 17 Bash blocks parse, Markdown fences close, 14 relative links resolve, whitespace passes, and private delivery copies match byte-for-byte. Existing CI must pass before merge; no CI waiver or image publication is requested.