| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [BUG] non archived WAL removed during production crash recovery |
| Date: | 2020-04-21 23:07:52 |
| Message-ID: | 20200421230752.GD33034@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Apr 22, 2020 at 12:00:22AM +0200, Jehan-Guillaume de Rorthais wrote:
> That leads me an idea where we would keep the ControlFile data up-to-date in
> shared memory. There's a few duplicates between ControlFile and XLogCtl, so
> maybe it could make the code a little simpler at some other places than just
> fixing $SUBJECT using DBState? I'm not sure of the implications and impacts
> though. This seems way bigger than the current fix and with many traps on the
> way. Maybe we could discuss this in another thread if you think it deserves it?
It seems to me that this could have wider applications than just the
recovery state, no? I would recommend to keep this discussion on a
separate thread to give more visibility to the topic.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2020-04-22 00:14:23 | Re: BUG #16354: No geos 3.8.1 package for RHEL 8 |
| Previous Message | Jehan-Guillaume de Rorthais | 2020-04-21 22:41:21 | Re: [BUG] non archived WAL removed during production crash recovery |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francois Payette | 2020-04-21 23:09:03 | MYSQL_FDW trigger BEFORE UPDATE changes to NEW on a col not in the update statement don't go through |
| Previous Message | Alvaro Herrera | 2020-04-21 23:03:30 | Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables |