Re: Timeline ID hexadecimal format

On 31/01/2023 20:16, Greg Stark wrote:
> The fact that the *filename* has it encoded in hex is an
> implementation detail and really gets exposed here because it's giving
> you the underlying system error that caused the problem.


It's an implementation detail, but an exposed detail, so, people refer 
to the filename to find the timeline ID (That's why it happened to me)


>   The confusion
> only arises when the two are juxtaposed. A hint or something just in
> that case might be enough?
>
>

Thanks, i got your point.

  Note that my proposal was to remove the ambiguous notation which 
happen in some case (as in 11 <-> 17). A hint is useless in most of the 
case, because there is no ambiguous. That's why i though format 
hexadecimal everywhere.


At least, can I propose to improve the documentation to expose the fact 
that the timeline ID is exposed in hexadecimal in filenames but must be 
used in decimal in recovery_target_timeline and pg_waldump ?


regards,

-- 
Sébastien