docs(targetTime): align documentation with cloudnative-pg #708
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
Update targetTime documentation to align with cloudnative-pg standards. The note now covers all timestamp formats (not just RFC 3339) and uses PostgreSQL format in the example to avoid advertising the non-standard RFC3339-like format without timezone. Add warning recommending to always specify an explicit timezone to avoid ambiguity. Related: #699 Signed-off-by: Marco Nenciarini <[email protected]>
dosubot
bot
added
size:S
NiccoloFei
approved these changes
Dec 30, 2025
leonardoce
approved these changes
Dec 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #700 to align the targetTime documentation with cloudnative-pg standards. The note now covers all timestamp formats (not just RFC 3339) and uses PostgreSQL format in the example to avoid advertising the non-standard RFC3339-like format without timezone. A warning has been added recommending to always specify an explicit timezone to avoid ambiguity.
Related: #699