comparison Sphinx/source/plugins/postgresql.rst @ 118:a30abf63ccba

postgres: reference to forum for space usage
author amazy
date Mon, 23 Oct 2017 09:39:56 +0200
parents b0a71b880ca0
children f2abbac22d5c
comparison
equal deleted inserted replaced
117:0a52547bc919 118:a30abf63ccba
80 80
81 Note that ``EnableIndex`` and ``EnableStorage`` must be explicitly set 81 Note that ``EnableIndex`` and ``EnableStorage`` must be explicitly set
82 to true, otherwise Orthanc will continue to use its default SQLite 82 to true, otherwise Orthanc will continue to use its default SQLite
83 back-end. 83 back-end.
84 84
85 **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). 85 **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).
86 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. 86
87 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.
88
89
87 90
88 .. highlight:: text 91 .. highlight:: text
89 92
90 Orthanc must of course be **restarted** after the modification of its 93 Orthanc must of course be **restarted** after the modification of its
91 configuration file. The log will contain an output similar to:: 94 configuration file. The log will contain an output similar to::