Re: standby recovery fails (tablespace related) (tentative patch and discussion)
От | Thomas Munro |
---|---|
Тема | Re: standby recovery fails (tablespace related) (tentative patch and discussion) |
Дата | |
Msg-id | CA+hUKGK9NaBvfmvCcangrqR2EZj0g0EBxCiaKiyv2zWuBfSceg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: standby recovery fails (tablespace related) (tentative patch and discussion) (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Re: standby recovery fails (tablespace related) (tentative patch and discussion) |
Список | pgsql-hackers |
On Mon, Mar 28, 2022 at 2:01 PM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > At Fri, 25 Mar 2022 13:26:05 +0100, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in > > Pushed this, backpatching to 14 and 13. It would have been good to > > backpatch further, but there's an (textually trivial) merge conflict > > related to commit e6d8069522c8. Because that commit conceptually > > touches the same area that this bugfix is about, I'm not sure that > > backpatching further without a lot more thought is wise -- particularly > > so when there's no way to automate the test in branches older than > > master. Just a thought: we could consider back-patching allow_in_place_tablespaces, after a little while, if we're happy with how that is working out, if it'd be useful for verifying bug fixes in back branches. It's non-end-user-facing testing infrastructure.
В списке pgsql-hackers по дате отправления: