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 <marco.nenciarini@enterprisedb.com>
This commit is contained in:
Marco Nenciarini 2025-12-30 12:24:25 +01:00
parent 1f1d30043b
commit 2dbc265387
No known key found for this signature in database
GPG Key ID: 589F03F01BA55038

View File

@ -359,8 +359,14 @@ For detailed Barman restore operations and troubleshooting, refer to the
``` ```
:::note :::note
RFC 3339 timestamps without an explicit timezone suffix Timestamps without an explicit timezone suffix
(e.g., `2024-01-15T10:30:00`) are interpreted as UTC. (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 :::note