# HG changeset patch
# User amazy
# Date 1508744396 -7200
# Node ID a30abf63ccba1c1aa648e36816cdbdb15e7bd68e
# Parent  0a52547bc9190202192c1fc73c49b80ae19e62d5
postgres: reference to forum for space usage

diff -r 0a52547bc919 -r a30abf63ccba Sphinx/source/plugins/postgresql.rst
--- 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