On Thu, Nov 16, 2017 at 7:08 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote: > Agreed, that's better. Attached updated patch. > Also I've added this to the next CF so as not to forget.
Committed and back-patched. While I'm fairly sure this is a correct fix, post-commit review from someone who knows GIN better than I do would be a great idea. I am also clear on what the consequences of this bug are. It seems like it could harm insert performance by making us wait when we shouldn't, but can it cause corruption? That I'm not sure about. If there's already a cleanup of the pending list in progress, how do things go wrong? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
