Howard Chu wrote:
Pierangelo Masarati wrote:
Gavin Henry wrote:
If this sounds so unreasonable, please suggest (and code) a better strategy. I'm open to everything (including zapping auditContext at all, unless anyone out there finds it useful and is actively using it).
Not unreasonable, just *totally* undocumented. It is, IMHO, a major missing part in the "Changes Since last version" section in the Admin Guide.
"major" ? Hardly.
Until I realised test43 passed, which it has done for ages ;-)
It's not even in *any* man pages in HEAD.
So Syncrepl won't work in 2.4 on any consumer, where the provider has accesslog enabled, i.e. delta-syncrepl.
Obviously that statement is false.
Yeah, but why on my setup has it broken?
Much appreciated for the feedback Ando. Time for me to get writing ;-)
Perhaps we should really find a better solution, rather than document a hack. What surprises me is that this change has been in HEAD (and, I believe, in 2.4) for at least a year, and nobody noticed it.
It went unnoticed because in general, it had zero impact. As Gavin pointed out, test043 still works fine, even without the schema definition.
I know. Confused again.