On Thu, Jun 30, 2016 at 5:38 PM, Stefan Eissing <[email protected]> wrote: > We now set exactly the same callback right before in line 709. If we had more > than one callback, we would not have to specify NULL, but restore any > previous callback there was, right?
Actually NULL preserves the current callback, so once we've set one (or the default) at global/connection init time, if we use NULL everywhere else we can preserve it (patch proposed in my previous message). > > But that is all just theoretical, as You and Yann already stated. Yes, this worked already like this in previous trunk and 2.4.x, even for the existing NULL below since we forcibly set it first.
