Re: Why don't update minimum recovery point in xact_redo_abort - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Why don't update minimum recovery point in xact_redo_abort
Date
Msg-id ab02ed2a-404a-314e-0b3e-d85b1c222c68@oss.nttdata.com
Whole thread Raw
In response to Re: Why don't update minimum recovery point in xact_redo_abort  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Why don't update minimum recovery point in xact_redo_abort  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers

On 2021/07/27 19:51, Michael Paquier wrote:
> On Tue, Jul 27, 2021 at 05:26:05PM +0900, Fujii Masao wrote:
>> ISTM that you're right. xact_redo_abort() should call XLogFlush() to
>> update the minimum recovery point on truncation. This seems
>> the oversight in commit 7bffc9b7bf.
> 
> Indeed.  It would be nice to see some refactoring of this code as
> well?  Both share a lot of steps, so adding something to one path can
> easily lead to the other path being forgotten.

That's idea, but as far as I read both functions, they seem not
so similar. So I'm not sure how much such refactoring would help.

Anyway I attached the patch that changes only xact_redo_abort()
so that it calls XLogFlush() to update min recovery point.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Inaccurate error message when set fdw batch_size to 0
Next
From: Andres Freund
Date:
Subject: Re: Removing "long int"-related limit on hash table sizes