large-objects in Postgresql database are not stored in a appropriate way for RHPAM 7
Issue
Regarding RHPAM and the handling of large objects in PostgreSQL database orphaned large objects are left in pg_largeobject, so users have to run manual operations to clean up orphaned large-object periodically. Run a vacuumlo is needed to prepare a database migration to another host or restore data from a backup when some data loss. This solution is not fit for use in a huge project.
- When do you plan to handle the data in a appropriate way?
- Which version will contain a real fix of the data model?
- How to use vacuumlo on PostgreSQL databases for RHPAM?
Environment
- Red Hat Process Automation Manager (RHPAM)
- 7.10.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.