On Fri, Jul 17, 2026 at 12:22 PM Thom Brown <[email protected]> wrote: > It's erroring out, but shouldn't it check for 000000020000000000000003 > before doing so? It wasn't removed, just renamed.
Actually, neither is the case. 000000010000000000000003 was not archived. 000000020000000000000003 is a different file with partially identical contents. But the fact that the existing error message here is not quite right is not a problem this patch should be trying to solve. -- Robert Haas EDB: http://www.enterprisedb.com
