Clarify NEWS on database "all" dump feature applying to MySQL as well.
This commit is contained in:
parent
301b29ee11
commit
4a90e090ad
1 changed files with 2 additions and 2 deletions
4
NEWS
4
NEWS
|
@ -1,6 +1,6 @@
|
||||||
1.7.6
|
1.7.6
|
||||||
* #393, #438, #560: Optionally dump "all" PostgreSQL databases to separate files instead of one
|
* #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of
|
||||||
combined dump file, allowing more convenient restores of individual databases. You can enable
|
one combined dump file, allowing more convenient restores of individual databases. You can enable
|
||||||
this by specifying the database dump "format" option when the database is named "all".
|
this by specifying the database dump "format" option when the database is named "all".
|
||||||
* #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
|
* #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
|
||||||
* #622: Fix traceback when include merging configuration files on ARM64.
|
* #622: Fix traceback when include merging configuration files on ARM64.
|
||||||
|
|
Loading…
Reference in a new issue