Is there any reason why pg_walfile_name() doesn't take timeline change into consideration?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Is there any reason why pg_walfile_name() doesn't take timeline change into consideration?
Date: 2026-05-18 12:27:08
Message-ID: agsFnCHnXlCoggik@depesz.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
I tried on a server that is on timeline 7 now, with .history being:

1 A9/5E0000A0 no recovery target specified
2 127/EB0000A0 no recovery target specified
3 127/F40000A0 no recovery target specified
4 128/170000A0 no recovery target specified
5 188/C70000A0 no recovery target specified
6 7B8/90000A0 no recovery target specified

When I wal file that is "current", i get sensible filename:

=# select pg_walfile_name('800/123');
pg_walfile_name
══════════════════════════
000000070000080000000000
(1 row)

But when I try to find walfile for old lsn, from older timeline, I'm getting bad results:

=# select pg_walfile_name('125/123');
pg_walfile_name
══════════════════════════
000000070000012500000000
(1 row)

Timeline 7 was was "there" when wal lsn was 125/…. Is it just missing
functionality, or am I missing something more complicated?

Best regards,

depesz

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2026-05-18 13:20:49 Re: REQ -POA on Minor Version upgrade
Previous Message Kristjan Mustkivi 2026-05-18 11:58:30 Re: REQ -POA on Minor Version upgrade