1MDB_DUMP(1)                 General Commands Manual                MDB_DUMP(1)
2
3
4

NAME

6       mdb_dump - LMDB environment export tool
7

SYNOPSIS

9       mdb_dump [-V] [-f file] [-l] [-n] [-p] [-a | -s subdb]  envpath
10

DESCRIPTION

12       The  mdb_dump  utility  reads a database and writes its contents to the
13       standard output using a portable flat-text  format  understood  by  the
14       mdb_load(1) utility.
15

OPTIONS

17       -V     Write  the  library  version  number to the standard output, and
18              exit.
19
20       -f file
21              Write to the specified file instead of to the standard output.
22
23       -l     List the databases stored in the  environment.  Just  the  names
24              will be listed, no data will be output.
25
26       -n     Dump an LMDB database which does not use subdirectories.
27
28       -p     If characters in either the key or data items are printing char‐
29              acters (as defined by isprint(3)), output  them  directly.  This
30              option  permits  users to use standard text editors and tools to
31              modify the contents of databases.
32
33              Note: different systems may have different  notions  about  what
34              characters  are  considered  printing  characters, and databases
35              dumped in this manner may be less portable to external systems.
36
37       -a     Dump all of the subdatabases in the environment.
38
39       -s subdb
40              Dump a specific subdatabase. If no database is  specified,  only
41              the main database is dumped.
42

DIAGNOSTICS

44       Exit  status  is  zero if no errors occur.  Errors result in a non-zero
45       exit status and a diagnostic message being written to standard error.
46
47       Dumping and reloading databases that use user-defined comparison  func‐
48       tions  will  result  in  new  databases that use the default comparison
49       functions.  In this case it is quite likely that the reloaded  database
50       will  be  damaged  beyond  repair permitting neither record storage nor
51       retrieval.
52
53       The  only  available  workaround  is  to  modify  the  source  for  the
54       mdb_load(1)  utility  to load the database using the correct comparison
55       functions.
56

SEE ALSO

58       mdb_load(1)
59

AUTHOR

61       Howard Chu of Symas Corporation <http://www.symas.com>
62
63
64
65LMDB 0.9.17                       2015/09/30                       MDB_DUMP(1)