Background：
・We plan to upgrade Sonatype Nexus from version 3.59 to 3.79.
・Since we are migrating from OrientDB, we understand that it is necessary to upgrade to 3.70 first as an intermediate step.
・Due to the requirements for the number of users, we need to migrate to PostgreSQL instead of H2.
・We are currently using an S3 blob store.
・The server in use is running RHEL 8.1.
I would appreciate it if you could provide information (more detailed description of the issue and the conditions under which the problem occurs) regarding the following issues listed in the Release Notes on the official Sonatype Nexus Repository page.
・Issue ID
Reason for inquiry
・NEXUS-46435
The problem description is not clear, and I would like to determine the impact of the bug.
https://help.sonatype.com/en/sonatype-nexus-repository-3-80-0-release-notes.html#bug-fixes-329581
・NEXUS-46937
I would like to confirm whether this issue applies when migrating from OrientDB → H2 → PostgreSQL.
https://help.sonatype.com/en/sonatype-nexus-repository-3-83-0-release-notes.html#bug-fixes-in-3-83-0
・NEXUS-45369
I would like to confirm whether this issue applies when migrating from OrientDB → H2 → PostgreSQL.
https://help.sonatype.com/en/sonatype-nexus-repository-3-83-0-release-notes.html#bug-fixes-in-3-83-0
・NEXUS-44970
The problem description is not clear, and I would like to determine the impact of the bug.
https://help.sonatype.com/en/sonatype-nexus-repository-3-84-0-release-notes.html#bug-fixes-in-3-84-0
・NEXUS-47252
I would like to confirm whether this issue applies when migrating from OrientDB → H2 → PostgreSQL.
https://help.sonatype.com/en/sonatype-nexus-repository-3-84-0-release-notes.html#bug-fixes-in-3-84-0
・NEXUS-46281
I would like to confirm whether this issue applies when migrating from OrientDB → H2 → PostgreSQL.
https://help.sonatype.com/en/sonatype-nexus-repository-3-85-0-release-notes.html#bug-fixes-450274
Thank you in advance for your cooperation.