On Wed, Aug 10, 2022 at 12:39 AM Thomas Munro <thomas.mu...@gmail.com> wrote: > Here's an email about that: > > https://www.postgresql.org/message-id/CAE9k0P=OXww6RQCGrmDNa8=L3EeB01SGbYuP23y-qZJ=4td...@mail.gmail.com
Hmm. If I'm reading that email correctly, it indicates that I noticed this problem before commit and asked for it to be changed, but then for some reason it wasn't changed and I still committed it. I can't immediately think of a reason why it wouldn't be safe to insist on acquiring a cleanup lock there. -- Robert Haas EDB: http://www.enterprisedb.com
