From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | thomas(dot)munro(at)gmail(dot)com |
Cc: | alvherre(at)alvh(dot)no-ip(dot)org, michael(at)paquier(dot)xyz, rjuju123(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: standby recovery fails (tablespace related) (tentative patch and discussion) |
Date: | 2022-03-28 06:25:51 |
Message-ID: | 20220328.152551.1598976250178471352.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Mon, 28 Mar 2022 14:34:44 +1300, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote in
> On Mon, Mar 28, 2022 at 2:01 PM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > At Fri, 25 Mar 2022 13:26:05 +0100, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.
I appreciate if we accept that. The patch is simple. And it now has
the clear use-case for back-patching.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-03-28 06:27:59 | Re: Logical replication timeout problem |
Previous Message | Dilip Kumar | 2022-03-28 06:18:22 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |