Thanks for the update, Sarah. Please clarify whether IBM was talking about the next PostgreSQL version or the next LLVM version that should fix this, as I don't see any IBM statement in the thread you linked to. BTW, I expect the next round of PostgreSQL minor releases in about a month, but AFAICS so far no fix for this issue has been committed.