public inbox for [email protected]
help / color / mirror / Atom feedrecovery_target_time format explanation should be clarified when using UTC zone
2+ messages / 2 participants
[nested] [flat]
* recovery_target_time format explanation should be clarified when using UTC zone
@ 2025-10-29 13:58 PG Doc comments form <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: PG Doc comments form @ 2025-10-29 13:58 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/index.html
Description:
We've been hitting a bug with PITR when specifying a recovery_target_time
with an ISO 8601 format and UTC zone indicated with a trailing `Z`.
We get an error like this
```
"msg":"waiting for server to start....2025-10-28 16:40:20.324 UTC [38]
LOG: invalid value for parameter \"recovery_target_time\": \"2025-10-28
16:34:15.000000Z\"",
```
The documentation states
> The value of this parameter is a time stamp in the same format accepted by
the timestamp with time zone data type, except that you cannot use a time
zone abbreviation
> [-snip-]
> Preferred style is to use a numeric offset from UTC, or you can write a
full time zone name, e.g., Europe/Helsinki not EEST.
That `Z`, if it's an abbreviation, would be an abbreviation for Zulu, I
presume? I tried to use `Zulu` and not just `z` but still had the same
`invalid value` error.
For timestamps in UTC zone, I think the only supported format would be
numeric offset, right? With `+00` instead of `Z`.
I think that the documentation should clarify this explicitly.
Unless there is a full name for the UTC zone which I'm unaware of...
Thanks
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: recovery_target_time format explanation should be clarified when using UTC zone
@ 2025-10-29 17:55 Jaime Silvela <[email protected]>
parent: PG Doc comments form <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Jaime Silvela @ 2025-10-29 17:55 UTC (permalink / raw)
To: Jaime Silvela <[email protected]>; [email protected]
Actually, I had not realized there was a “Submit Correction” link on each documentation page.
Sorry, hope I haven’t made this confusing.
The documentation page that requires clarification is
https://www.postgresql.org/docs/current/runtime-config-wal.html#RUNTIME-CONFIG-WAL-RECOVERY-TARGET�...
19.5. Write Ahead Log
postgresql.org
> On 29 Oct 2025, at 14:58, PG Doc comments form <[email protected]> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/index.html
> Description:
>
> We've been hitting a bug with PITR when specifying a recovery_target_time
> with an ISO 8601 format and UTC zone indicated with a trailing `Z`.
>
> We get an error like this
>
> ```
> "msg":"waiting for server to start....2025-10-28 16:40:20.324 UTC [38]
> LOG: invalid value for parameter \"recovery_target_time\": \"2025-10-28
> 16:34:15.000000Z\"",
> ```
>
> The documentation states
>
>> The value of this parameter is a time stamp in the same format accepted by
> the timestamp with time zone data type, except that you cannot use a time
> zone abbreviation
>> [-snip-]
>> Preferred style is to use a numeric offset from UTC, or you can write a
> full time zone name, e.g., Europe/Helsinki not EEST.
>
> That `Z`, if it's an abbreviation, would be an abbreviation for Zulu, I
> presume? I tried to use `Zulu` and not just `z` but still had the same
> `invalid value` error.
>
> For timestamps in UTC zone, I think the only supported format would be
> numeric offset, right? With `+00` instead of `Z`.
> I think that the documentation should clarify this explicitly.
> Unless there is a full name for the UTC zone which I'm unaware of...
>
> Thanks
Attachments:
[image/png] elephant.png (49.1K, 3-elephant.png)
download | view image
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-10-29 17:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-10-29 13:58 recovery_target_time format explanation should be clarified when using UTC zone PG Doc comments form <[email protected]>
2025-10-29 17:55 ` Jaime Silvela <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox