diff --git a/MANIFEST.in b/MANIFEST.in
index 807e2e9..25320bc 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -1,5 +1,6 @@
 include Makefile
 include requirements*.txt
 include version.txt
 include README.md
 recursive-include swh py.typed
+recursive-include swh/scrubber/sql *
diff --git a/PKG-INFO b/PKG-INFO
index 40ef69a..32edb0f 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,61 +1,61 @@
 Metadata-Version: 2.1
 Name: swh.scrubber
-Version: 0.0.3
+Version: 0.0.4
 Summary: Software Heritage Datastore Scrubber
 Home-page: https://forge.softwareheritage.org/diffusion/swh-scrubber
 Author: Software Heritage developers
 Author-email: swh-devel@inria.fr
 Project-URL: Bug Reports, https://forge.softwareheritage.org/maniphest
 Project-URL: Funding, https://www.softwareheritage.org/donate
 Project-URL: Source, https://forge.softwareheritage.org/source/swh-scrubber
 Project-URL: Documentation, https://docs.softwareheritage.org/devel/swh-scrubber/
 Classifier: Programming Language :: Python :: 3
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
 Classifier: Operating System :: OS Independent
 Classifier: Development Status :: 3 - Alpha
 Requires-Python: >=3.7
 Description-Content-Type: text/x-rst
 Provides-Extra: testing
 License-File: LICENSE
 License-File: AUTHORS
 
 Software Heritage - Datastore Scrubber
 ======================================
 
 Tools to periodically checks data integrity in swh-storage and swh-objstorage,
 reports errors, and (try to) fix them.
 
 This is a work in progress; some of the components described below do not
 exist yet (cassandra storage checker, objstorage checker, recovery, and reinjection)
 
 The Scrubber package is made of the following parts:
 
 
 Checking
 --------
 
 Highly parallel processes continuously read objects from a data store,
 compute checksums, and write any failure in a database, along with the data of
 the corrupt object.
 
 There is one "checker" for each datastore package: storage (postgresql and cassandra),
 journal (kafka), and objstorage.
 
 
 Recovery
 --------
 
 Then, from time to time, jobs go through the list of known corrupt objects,
 and try to recover the original objects, through various means:
 
 * Brute-forcing variations until they match their checksum
 * Recovering from another data store
 * As a last resort, recovering from known origins, if any
 
 
 Reinjection
 -----------
 
 Finally, when an original object is recovered, it is reinjected in the original
 data store, replacing the corrupt one.
diff --git a/swh.scrubber.egg-info/PKG-INFO b/swh.scrubber.egg-info/PKG-INFO
index 40ef69a..32edb0f 100644
--- a/swh.scrubber.egg-info/PKG-INFO
+++ b/swh.scrubber.egg-info/PKG-INFO
@@ -1,61 +1,61 @@
 Metadata-Version: 2.1
 Name: swh.scrubber
-Version: 0.0.3
+Version: 0.0.4
 Summary: Software Heritage Datastore Scrubber
 Home-page: https://forge.softwareheritage.org/diffusion/swh-scrubber
 Author: Software Heritage developers
 Author-email: swh-devel@inria.fr
 Project-URL: Bug Reports, https://forge.softwareheritage.org/maniphest
 Project-URL: Funding, https://www.softwareheritage.org/donate
 Project-URL: Source, https://forge.softwareheritage.org/source/swh-scrubber
 Project-URL: Documentation, https://docs.softwareheritage.org/devel/swh-scrubber/
 Classifier: Programming Language :: Python :: 3
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
 Classifier: Operating System :: OS Independent
 Classifier: Development Status :: 3 - Alpha
 Requires-Python: >=3.7
 Description-Content-Type: text/x-rst
 Provides-Extra: testing
 License-File: LICENSE
 License-File: AUTHORS
 
 Software Heritage - Datastore Scrubber
 ======================================
 
 Tools to periodically checks data integrity in swh-storage and swh-objstorage,
 reports errors, and (try to) fix them.
 
 This is a work in progress; some of the components described below do not
 exist yet (cassandra storage checker, objstorage checker, recovery, and reinjection)
 
 The Scrubber package is made of the following parts:
 
 
 Checking
 --------
 
 Highly parallel processes continuously read objects from a data store,
 compute checksums, and write any failure in a database, along with the data of
 the corrupt object.
 
 There is one "checker" for each datastore package: storage (postgresql and cassandra),
 journal (kafka), and objstorage.
 
 
 Recovery
 --------
 
 Then, from time to time, jobs go through the list of known corrupt objects,
 and try to recover the original objects, through various means:
 
 * Brute-forcing variations until they match their checksum
 * Recovering from another data store
 * As a last resort, recovering from known origins, if any
 
 
 Reinjection
 -----------
 
 Finally, when an original object is recovered, it is reinjected in the original
 data store, replacing the corrupt one.