On Jul 10, 2025, at 13:41, Florents Tselai <florents.tse...@gmail.com> wrote:
> The basic problem I see with these latest revisions/refactorings is that they > fail for pg_upgrade afaict. > Probably this means that some of the rearrangements on the parser/scanner are > not that flexible. Oh, is that what’s happening? What needs to happen to properly support pg_upgrade? Best, David
signature.asc
Description: Message signed with OpenPGP
