Age | Commit message (Collapse) | Author | Files | Lines |
|
Changelog diff is:
diff --git a/Changes b/Changes
index f77e9f9..cd1a4c3 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.4.1 2020-09-27T12:57:01Z
- Fix missing cache data for files that exist with and without an
extension. For example '/home/*/.ssh/id_rsa' would be missing from the
database and only the accompanying `id_rsa.pub` file would be contained
|
|
previous path
Files that share a common substring (e.g. `/home/foo/.ssh/id_rsa` and
`/home/foo/.ssh/id_rsa.pub`) could incorrectly trigger an optimization
that was only supposed to be triggered if the first path is a directory.
The first path would then not be added to the database cache even though
it should have been.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index eeb4d3b..dd5812e 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.4.0 2019-09-28T13:28:49Z
- Remove archive name untaint restrictions (remove untaint_archive_name
function)
|
|
Better code readability than with the full name.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
We no longer need a special whitelist for archive names since the
database no longer uses them as column keys. We still need to untaint
variables that are passed to DBI so we use untaint() for this now. We
also move the location of the untaint call closer to its usage with
DBI/system() to prevent untainted data from leaking elsewhere.
Fixes #4
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Having the backup archive names in the table columns is not strictly
necessary. Replace this with numeric IDs and map them via the `archives`
table so that we can eventually remove untaint_archive_name().
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index 807706c..9bb5022 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.3.0 2019-02-07T16:18:41Z
- Support borg list's --prefix option via $borg_prefix setting
- Properly handle cases where the DB is empty after removal of archive
information
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Empty here means that the DB does not contain any backup archive
information because all information that is already in the db has to be
removed. The old code tries to copy existing data into the new table,
but since there are no archives to copy data for, the sql query fails.
Also, it would copy all rows and only populate the path column, but if
there are no archives that have timestamps, that's actually useless
work.
This patch ensures that the table is kept empty if there are no
archives.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index b9b6218..dae2435 100644
--- a/Changes
+++ b/Changes
@@ -2,6 +2,9 @@ Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+3.2.1 2018-11-01T12:54:26Z
+ - Add missing version requirement to List::Util dependency
+
3.2.0 2018-09-19T11:46:35Z
- Write data directly to DB instead of preparing it in memory first. The
new algorithm should be faster and uses constant memory. If you want the
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index bd95acb..b9b6218 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.2.0 2018-09-19T11:46:35Z
- Write data directly to DB instead of preparing it in memory first. The
new algorithm should be faster and uses constant memory. If you want the
old one back for any reason look at the '$prepare_data_in_memory' config
|
|
Also instantly deprecate the option since it is only a short term fix in
case someone notices problems with the new code.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
removing an item from the stack
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This cuts execution time on my workstation from about 85 seconds for an
--update-cache adding one archive to roughly 62 seconds. Measured
totally unscientifically by simply running the full application instead
of isolating the code, but it makes sense that regexes are slower so
I'll take it.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index a4b127d..a7d4b7b 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.1.0 2018-08-25T09:46:27Z
- Add --json option
- Add --detail option
- Log cache update status message per archive to INFO
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
The original performance problem on my machine doesn't seem to be
reproducable any more so maybe either sqlite got smarter or it was
something else entirely. Move the warning to DEBUG and soften the
documentation. If it still helps people can use it, but we don't have to
annoy them if it doesn't.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index 22043d6..600f118 100644
--- a/Changes
+++ b/Changes
@@ -1,6 +1,8 @@
Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+
+3.0.0 2018-03-23T14:57:52Z
- No longer automatically enable --adhoc when cache is empty
2.3.0 2018-02-06T15:58:36Z
|
|
Changelog diff is:
diff --git a/Changes b/Changes
index 32e7b5b..a46f8bc 100644
--- a/Changes
+++ b/Changes
@@ -2,6 +2,11 @@ Revision history for Perl extension App-BorgRestore
{{$NEXT}}
+2.3.0 2018-02-06T15:58:36Z
+ - Add --list option to search for paths occuring in backups
+ - Warn if sqlite's memory cache is is filled during cache updates
+ - Improve documentation of @backup_prefixes setting
+
2.2.0 2017-11-25T23:16:04Z
- Add borg 1.1 support
- Mention required positive return code of config in documentation
|
|
While not all operations fill the cache, --list does. However, for read
operations it doesn't actually appear to help performance. Limit the
large cache setting to update operations only because there it does
really increase performance.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|