[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Value of contextCSN not persisted

Torsten Schlabach (Tascel eG) wrote:
Hi Quanah!

First of all: Thanks for answering the original question. I was wondering
first why changes to the database content as such have been persisted and
the new contextCSN hasn't until I found that this syncprov-checkpoint thing
actually belongs to the syncprov overlay. So I guess it makes sense to
switch that on as otherwise - for example after a power failure - I would
have lost information, wouldn't I?

No, of course not. If there was a danger of data loss we certainly would not leave that as the default behavior.

In fact the syncprov overlay always reads the largest entryCSN out of the database at startup time anyway, so even if it didn't save the contextCSN before stopping, it will be up to date on every startup. Checkpointing the CSN is only an optimization, it will reduce the length of the search time on the next startup.

  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/