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

From Tom Lane
Subject Re: pendingOps table is not cleared with fsync=off
Date
Msg-id 2629130.1596728520@sss.pgh.pa.us
Whole thread Raw
In response to Re: pendingOps table is not cleared with fsync=off  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: pendingOps table is not cleared with fsync=off
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: FailedAssertion("pd_idx == pinfo->nparts", File: "execPartition.c", Line: 1689)
Next
From: Robert Haas
Date:
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."