| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | dilipbalaut(at)gmail(dot)com |
| Cc: | robertmhaas(at)gmail(dot)com, 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-04-05 07:38:06 |
| Message-ID: | 20220405.163806.716548871041426622.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 05 Apr 2022 11:16:44 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> So, I have the following points in my mind for now.
>
> - We create the directory "since we know it is just tentative state".
>
> - Then, check that no directory in pg_tblspc when reaching consistency
> when allow_in_place_tablespaces is false.
>
> - Leave the log_invalid_page() mechanism alone as it is always result
> in a corrpt page if a differential WAL record is applied on a newly
> created page that should have been exist.
>
> However, while working on it, I found that I found that recovery faces
> missing tablespace directories *after* reaching consistency. I'm
> examining that further.
Okay, it was my thinko. But I faced another obstacle.
This is the first cut of the above.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| v22-0001-Fix-replay-of-create-database-records-on-standby.patch | text/x-patch | 18.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2022-04-05 07:38:44 | Re: Window Function "Run Conditions" |
| Previous Message | gkokolatos | 2022-04-05 07:13:35 | Re: Add LZ4 compression in pg_dump |