From 2dbc2653870b7b7e467173e9d35385b933006b95 Mon Sep 17 00:00:00 2001 From: Marco Nenciarini Date: Tue, 30 Dec 2025 12:24:25 +0100 Subject: [PATCH] docs(targetTime): align documentation with cloudnative-pg 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 --- web/docs/troubleshooting.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/web/docs/troubleshooting.md b/web/docs/troubleshooting.md index 4a8f0ea3..9441cb8a 100644 --- a/web/docs/troubleshooting.md +++ b/web/docs/troubleshooting.md @@ -359,8 +359,14 @@ For detailed Barman restore operations and troubleshooting, refer to the ``` :::note -RFC 3339 timestamps without an explicit timezone suffix -(e.g., `2024-01-15T10:30:00`) are interpreted as UTC. +Timestamps without an explicit timezone suffix +(e.g., `2024-01-15 10:30:00`) are interpreted as UTC. +::: + +:::warning +Always specify an explicit timezone in your timestamp to avoid ambiguity. +For example, use `2024-01-15T10:30:00Z` or `2024-01-15T10:30:00+02:00` +instead of `2024-01-15 10:30:00`. ::: :::note