From 00aa5fdeac40bba39e8a17b790a168234557acea Mon Sep 17 00:00:00 2001 From: Marco Nenciarini Date: Wed, 24 Dec 2025 14:27:41 +0100 Subject: [PATCH] fix(targetTime): treat RFC3339-like timestamps without timezone as UTC Update the machinery dependency to include the fix that ensures RFC3339-like timestamps without timezone (e.g., "2024-01-15T10:30:00") are interpreted as UTC. The documentation has been updated to use a targetTime example with an explicit Z suffix and to clarify that timestamps without timezone are interpreted as UTC. Closes #699 Signed-off-by: Marco Nenciarini --- web/docs/troubleshooting.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/web/docs/troubleshooting.md b/web/docs/troubleshooting.md index 132916b..4a8f0ea 100644 --- a/web/docs/troubleshooting.md +++ b/web/docs/troubleshooting.md @@ -339,7 +339,7 @@ For detailed Barman restore operations and troubleshooting, refer to the recovery: source: origin recoveryTarget: - targetTime: "2024-01-15 10:30:00" + targetTime: "2024-01-15T10:30:00Z" externalClusters: - name: origin @@ -358,6 +358,11 @@ For detailed Barman restore operations and troubleshooting, refer to the -c plugin-barman-cloud | grep -i wal ``` +:::note +RFC 3339 timestamps without an explicit timezone suffix +(e.g., `2024-01-15T10:30:00`) are interpreted as UTC. +::: + :::note For detailed PITR configuration and WAL management, see the [Barman PITR documentation](https://docs.pgbarman.org/latest/).