changeset 118:a30abf63ccba

postgres: reference to forum for space usage
author amazy
date Mon, 23 Oct 2017 09:39:56 +0200
parents 0a52547bc919
children a4f392011021 1defc59e3efa 9d80782b39d8
files Sphinx/source/plugins/postgresql.rst
diffstat 1 files changed, 5 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/Sphinx/source/plugins/postgresql.rst	Thu Oct 05 17:06:14 2017 +0200
+++ b/Sphinx/source/plugins/postgresql.rst	Mon Oct 23 09:39:56 2017 +0200
@@ -82,8 +82,11 @@
 to true, otherwise Orthanc will continue to use its default SQLite
 back-end.
 
-**Remark:** When using the ``Storage`` PostgreSQL plugin, the DICOM files are stored as large objects in the database.  This actually consumes more space than the DICOM file itself (around 40% more).  
-When dealing with large  number of files, it is recommended to continue using the default filesystem storage for DICOM files and enable the ``Index`` PostgreSQL plugin.
+**Remark:** When using the ``Storage`` PostgreSQL plugin, the DICOM files are stored as large objects in the database.  This might actually consume more space than the DICOM file itself.  We have observed overhead up to 40%.  However, it seems this overhead is temporary and comes from Write-Ahead Logging.  Check this `discussion <https://groups.google.com/d/msg/orthanc-users/pPzHOpb--iw/QkKZ808gIgAJ>`__ on the Orthanc Users group for more info).  
+
+Note that a typical usage of the PostgreSQL plugin is to enable only the ``Index`` and continue using the default filesystem storage for DICOM files.
+
+
 
 .. highlight:: text