Re: Incorrect handling of OOM in WAL replay leading to data loss

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, ethmertz(at)amazon(dot)com, nathandbossart(at)gmail(dot)com, pgsql(at)j-davis(dot)com, sawada(dot)mshk(at)gmail(dot)com
Subject: Re: Incorrect handling of OOM in WAL replay leading to data loss
Date: 2023-10-24 04:56:10
Message-ID: ZTdOalhqXp7GS36a@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 03, 2023 at 04:20:45PM +0900, Michael Paquier wrote:
> If there's no interest in this patch set after the next CF, I'm OK to
> drop it. The state of HEAD is at least correct in the OOM cases now.

I have been thinking about this patch for the last few days, and in
light of 6b18b3fe2c2f I am going to withdraw it for now as this makes
the error layers of the xlogreader more complicated.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirk Wolak 2023-10-24 05:09:48 Re: psql: Could we get "-- " prefixing on the **** QUERY **** outputs? (ECHO_HIDDEN)
Previous Message Michael Paquier 2023-10-24 04:31:32 Re: run pgindent on a regular basis / scripted manner