You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1a64853
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(targetTime): clarify timestamp formats and UTC interpretation (#8937)
Update the machinery dependency to v0.3.3 to ensure timestamps without
timezone (both RFC3339 and PostgreSQL formats) are interpreted as UTC.
The documentation has been updated to clarify that targetTime accepts
both RFC 3339 and PostgreSQL timestamp formats.
Closes#8928
Related: cloudnative-pg/machinery#167
Signed-off-by: Pierrick Chovelon <[email protected]>
Signed-off-by: Pierrick <[email protected]>
Signed-off-by: Marco Nenciarini <[email protected]>
Signed-off-by: Armando Ruocco <[email protected]>
Co-authored-by: Jaime Silvela <[email protected]>
Co-authored-by: Marco Nenciarini <[email protected]>
Co-authored-by: Armando Ruocco <[email protected]>
Copy file name to clipboardExpand all lines: docs/src/cloudnative-pg.v1.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2232,7 +2232,7 @@ _Appears in:_
2232
2232
|`targetXID`_string_| The target transaction ID ||||
2233
2233
|`targetName`_string_| The target name (to be previously created<br />with `pg_create_restore_point`) ||||
2234
2234
|`targetLSN`_string_| The target LSN (Log Sequence Number) ||||
2235
-
|`targetTime`_string_| The target time as a timestamp in the RFC3339 standard||||
2235
+
|`targetTime`_string_| The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.<br />Timestamps without an explicit timezone are interpreted as UTC.||||
2236
2236
|`targetImmediate`_boolean_| End recovery as soon as a consistent state is reached ||||
2237
2237
|`exclusive`_boolean_| Set the target to be exclusive. If omitted, defaults to false, so that<br />in Postgres, `recovery_target_inclusive` will be true ||||
0 commit comments