On Tue, Jun 9, 2020 at 3:37 PM Andres Freund <and...@anarazel.de> wrote: > Hm. Looking at this again, perhaps the better fix would be to simply not > look at the concrete values of the barrier inside the signal handler? > E.g. we could have a new PROCSIG_GLOBAL_BARRIER, which just triggers > ProcSignalBarrierPending to be set. And then have > ProcessProcSignalBarrier do the check that's currently in > CheckProcSignalBarrier()?
That seems like a good idea. Also, I wonder if someone would be willing to set up a BF animal for this. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
