Re: [PoC] pg_upgrade: allow to upgrade publisher node
От | Amit Kapila |
---|---|
Тема | Re: [PoC] pg_upgrade: allow to upgrade publisher node |
Дата | |
Msg-id | CAA4eK1JcgAgj_XMBaYr=DkQ1669FLYLGSiA-FUPkuRmQYXGaqQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PoC] pg_upgrade: allow to upgrade publisher node (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: [PoC] pg_upgrade: allow to upgrade publisher node
|
Список | pgsql-hackers |
On Fri, Oct 27, 2023 at 10:43 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Fri, Oct 27, 2023 at 04:40:43AM +0000, Hayato Kuroda (Fujitsu) wrote: > > Yeah, Bharath has already reported, I agreed that the reason was [1]. > > > > ``` > > In the Windows API (with some exceptions discussed in the following paragraphs), > > the maximum length for a path is MAX_PATH, which is defined as 260 characters. > > ``` > > - "invalid_logical_replication_slots.txt"); > + "invalid_logical_slots.txt"); > > Or you could do something even shorter, with "invalid_slots.txt". > I also thought of it but if we want to keep it that way, we should slightly adjust the messages like: "The slot \"%s\" is invalid" to include slot_type. This will contain only logical slots, so the current one probably seems okay. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: