On Sat, May 4, 2019 at 2:17 PM Michael Paquier <mich...@paquier.xyz> wrote: > > On Sat, May 04, 2019 at 04:34:59PM +0530, Amit Kapila wrote: > > The fix looks good to me as well. > > We are very close to the next minor release, so it may not be that > wise to commit a fix for that issue now as we should have a couple of > clean buildfarm clean runs.
Agreed. > Are there any objections to wait after > the release? Or would folks prefer if this is fixed before the > release? No objection from me. It's been broken since introduction in 9.5 and has never been noticed since, so it can wait until next release. Should I register the patch in the next commitfest to keep track of it?
