Some issues customers are encountering on RHPAM due to the usage of @Lob -> oid columns:

1. oid columns use an auto-incrementing integer value that is unique within a Postgres instance with a range of 2^32. Customer expects this limit to be reached in ~2 years.
2. When running Postgres on AWS with rotating userids via Vault, customers run into permission issues for oid columns when users are rotated. The required setting to work around this (lo_compat_privilege option=true) is not allowed on AWS.
3. The large objects table is not automatically cleaned up when related entries are removed from the DB. We have a documented approach on how to perform a manual cleanup, but this requires manual intervention and thus imposes operational overhead.