Re: pendingOps table is not cleared with fsync=off - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: pendingOps table is not cleared with fsync=off
Date
Msg-id 35a4a635-08c6-05cf-ebce-6a51cf0c91e6@iki.fi
Whole thread Raw
In response to Re: pendingOps table is not cleared with fsync=off  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pendingOps table is not cleared with fsync=off  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 06/08/2020 18:42, Tom Lane wrote:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
>> On 09/05/2020 02:53, Thomas Munro wrote:
>>> On Sat, May 9, 2020 at 9:21 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>>>> I noticed that commit 3eb77eba5a changed the logic in
>>>> ProcessSyncRequests() (formerly mdsync()) so that if you have fsync=off,
>>>> the entries are not removed from the pendingOps hash table. I don't
>>>> think that was intended.
> 
> I'm looking at this commit in connection with writing release notes
> for next week's releases.  Am I right in thinking that this bug leads
> to indefinite bloat of the pendingOps hash table when fsync is off?
> If so, that seems much more worth documenting than the assertion
> failure.

That's correct.

- Heikki



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: new heapcheck contrib module
Next
From: Tom Lane
Date:
Subject: Re: pendingOps table is not cleared with fsync=off