On Tue, 1 Oct 2013, Howard Chu wrote:
Fixing this will either require adding a bunch of ugly code, or changing the
on-disk format again. Opinions?
Interesting...I think this might be the same issue that hit sparcv9
=2.4.32.
http://www.openldap.org/lists/openldap-devel/201207/msg00017.html
Fixing this will either require adding a bunch of ugly code, or changing the
on-disk format again. Opinions?
Currently the page in-use offsets mp_lower and mp_upper range from [PAGEHDRSZ
to pagesize]. IMO this was a stupid choice, carried over from the original
btree code. It should instead
On Tue, 01 Oct 2013 01:34:20 -0700 Howard Chu h...@symas.com wrote
Fixing this will either require adding a bunch of ugly code, or changing the
on-disk format again. Opinions?
I'd vote for changing the on-disk format.
Simpler code will be easier to maintain and that's good in the long run.
Howard Chu writes:
Fixing this will either require adding a bunch of ugly code, or
changing the on-disk format again. Opinions? (...) Adjusting
this would require only a few minor tweaks to the code, but
would require a full dump/reload of existing databases.
Then I hope for the format
--On Tuesday, October 01, 2013 1:34 AM -0700 Howard Chu h...@symas.com
wrote:
Fixing this will either require adding a bunch of ugly code, or changing
the on-disk format again. Opinions?
Currently the page in-use offsets mp_lower and mp_upper range from
[PAGEHDRSZ to pagesize]. IMO this was a
