Postgres Pro
Downloads
Home   >   mailing lists

Re: PANIC: could not fsync file "pg_multixact/..." since commit dee663f7843 - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: PANIC: could not fsync file "pg_multixact/..." since commit dee663f7843
Date
Msg-id CA+hUKG+c+Rtz3JuXBK=+tWZa4F=3w5eFA97MTAzZKER2ARF_0A@mail.gmail.com
Whole thread Raw
In response to PANIC: could not fsync file "pg_multixact/..." since commit dee663f7843  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: PANIC: could not fsync file "pg_multixact/..." since commit dee663f7843  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Wed, Nov 4, 2020 at 2:32 PM Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> After a while (~1h on my machine) the pg_multixact gets over 10GB, which
> triggers a more aggressive cleanup (per MultiXactMemberFreezeThreshold).
> My guess is that this discards some of the files, but checkpointer is
> not aware of that, or something like that. Not sure.

Urgh.  Thanks.  Looks like perhaps the problem is that I have
RegisterSyncRequest(&tag, SYNC_FORGET_REQUEST, true) in one codepath
that unlinks files, but not another.  Looking.

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Explicit NULL dereference (src/backend/utils/adt/ruleutils.c)
Next
From: David Rowley
Date:
Subject: Re: Collation versioning