mdb_dump.1 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475
  1. .TH MDB_DUMP 1 "2015/09/30" "LMDB 0.9.17"
  2. .\" Copyright 2014-2021 Howard Chu, Symas Corp. All Rights Reserved.
  3. .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
  4. .SH NAME
  5. mdb_dump \- LMDB environment export tool
  6. .SH SYNOPSIS
  7. .B mdb_dump
  8. [\c
  9. .BR \-V ]
  10. [\c
  11. .BI \-f \ file\fR]
  12. [\c
  13. .BR \-l ]
  14. [\c
  15. .BR \-n ]
  16. [\c
  17. .BR \-p ]
  18. [\c
  19. .BR \-a \ |
  20. .BI \-s \ subdb\fR]
  21. .BR \ envpath
  22. .SH DESCRIPTION
  23. The
  24. .B mdb_dump
  25. utility reads a database and writes its contents to the
  26. standard output using a portable flat-text format
  27. understood by the
  28. .BR mdb_load (1)
  29. utility.
  30. .SH OPTIONS
  31. .TP
  32. .BR \-V
  33. Write the library version number to the standard output, and exit.
  34. .TP
  35. .BR \-f \ file
  36. Write to the specified file instead of to the standard output.
  37. .TP
  38. .BR \-l
  39. List the databases stored in the environment. Just the
  40. names will be listed, no data will be output.
  41. .TP
  42. .BR \-n
  43. Dump an LMDB database which does not use subdirectories.
  44. .TP
  45. .BR \-p
  46. If characters in either the key or data items are printing characters (as
  47. defined by isprint(3)), output them directly. This option permits users to
  48. use standard text editors and tools to modify the contents of databases.
  49. Note: different systems may have different notions about what characters
  50. are considered printing characters, and databases dumped in this manner may
  51. be less portable to external systems.
  52. .TP
  53. .BR \-a
  54. Dump all of the subdatabases in the environment.
  55. .TP
  56. .BR \-s \ subdb
  57. Dump a specific subdatabase. If no database is specified, only the main database is dumped.
  58. .SH DIAGNOSTICS
  59. Exit status is zero if no errors occur.
  60. Errors result in a non-zero exit status and
  61. a diagnostic message being written to standard error.
  62. Dumping and reloading databases that use user-defined comparison functions
  63. will result in new databases that use the default comparison functions.
  64. \fBIn this case it is quite likely that the reloaded database will be
  65. damaged beyond repair permitting neither record storage nor retrieval.\fP
  66. The only available workaround is to modify the source for the
  67. .BR mdb_load (1)
  68. utility to load the database using the correct comparison functions.
  69. .SH "SEE ALSO"
  70. .BR mdb_load (1)
  71. .SH AUTHOR
  72. Howard Chu of Symas Corporation <http://www.symas.com>