Re: pendingOps table is not cleared with fsync=off

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shawn Debnath <sdn(at)amazon(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pendingOps table is not cleared with fsync=off
Date: 2020-08-10 18:50:26
Message-ID: 3247004.1597085426@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shawn Debnath <sdn(at)amazon(dot)com> writes:
> Good catch. Question is, are the users aware of the requirement to do a
> manual fsync if they flip the fsync GUC off and then on? Should we do
> this on their behalf to make a good faith attempt to ensure things are
> flushed properly via an assign hook?

No. Or at least, expecting that you can do that from an assign hook
is impossibly wrong-headed. GUC assign hooks can't have failure modes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-08-10 19:33:15 Re: Issue with cancel_before_shmem_exit while searching to remove a particular registered exit callbacks
Previous Message Anastasia Lubennikova 2020-08-10 17:30:44 Re: [BUG] Error in BRIN summarization