Good afternoon, we have a database in postgres, we are using slony-i to replicate, but there are some tables with an error for not having a primary key.
-deletedfiles
-deletedresources
-remainingancestor
Are these tables really important or do they not affect replication?
Another question.
We have the files on one disk, when it is full, can we add another one and use it together with the previous one? or should we create a new bigger one?
Hello,
Those 3 tables are only transiently used within a transaction to give information to the C++ code about the deletion of some DICOM resources. As a consequence, they can be ignored in a backup.
If Orthanc uses the default storage area (on the filesystem), you’ll have to create a new bigger one. To avoid this issue in the future, you could make Orthanc use a clustered filesystem that provides native extension mechanisms (such as Lustre):
https://en.wikipedia.org/wiki/Clustered_file_system
If you use the PostgreSQL/MySQL storage backend, those databases provide mechanisms to extend their disk space in a more flexible way.
You could also create a new plugin that would implement a custom storage area through sharding:
http://sdk.orthanc-server.com/ (check out “OrthancPluginRegisterStorageArea()”)
http://book.orthanc-server.com/developers/creating-plugins.html
Regards,
Sébastien-