Is there any chance this fix will get into the next minor version of PostgreSQL scheduled for February?