| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | thomas(dot)munro(at)gmail(dot)com, dilipbalaut(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, 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-07-22 08:18:58 |
| Message-ID: | 20220722081858.omhn2in5zt3g4nek@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Jul-22, Kyotaro Horiguchi wrote:
> At Thu, 21 Jul 2022 23:14:57 +1200, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote in
> > Would it help if we back-patched the allow_in_place_tablespaces stuff?
> > I'm not sure how hard/destabilising that would be, but I could take a
> > look tomorrow.
>
> +1. Addiotional reason for me is it is a developer option.
OK, I'll wait for allow_in_place_tablespaces to be backpatched then.
I would like to get this fix pushed before the next set of minors, so if
you won't have time for the backpatches early enough, maybe I can work
on getting it done.
Which commits would we consider?
7170f2159fb2 Allow "in place" tablespaces.
f6f0db4d6240 Fix pg_tablespace_location() with in-place tablespaces
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Most hackers will be perfectly comfortable conceptualizing users as entropy
sources, so let's move on." (Nathaniel Smith)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 王伟 (学弈) | 2022-07-22 08:22:46 | PANIC: wrong buffer passed to visibilitymap_clear |
| Previous Message | Kyotaro Horiguchi | 2022-07-22 08:17:12 | Re: Remove useless arguments in ReadCheckpointRecord(). |