Best practices for opening and recovering? about goleveldb HOT 2 CLOSED

The Open and Recover calls seem to accomplish the same thing (opening a database) with separate limitations; the Open calls can create a database but not open a corrupt one, while Recover can open a corrupt database (for specific values of corrupt) but not create one.

Recover is expensive, it scans all tables for corruption and rebuilding it if necessary (table scans also needed in order to extract latest sequence number).

Assuming one always wants to make a best effort to open a database, is best practice to use Open and retry with Recover if Open failed? Or start with Recover and use Open if the db did not exist?

Open and retry with Recover is the way to go. Open will return error with type of ErrCorrupted if it fails due to corruption.

Or else? What is the risk/downside of exiting abruptly without close - corruption, or just a non-compact database or similar? Will that be fixed on open, or only on recover?

Exiting abruptly without close should not cause corruption. But it is a best practice to close the DB before exiting.

from goleveldb.

Gotcha. Thanks for clarifying.

from goleveldb.