The LDF has been administrating the consolidated DB environment. Since the beginning of the LDF, Oracle has been the database of choice for the consolidated DB. Oracle was chosen based on scalability of the data and admin domain knowledge based on previous astronomy projects at the LDF. NCSA still believes that as of operations year 4-5 with the current data design that most databases will have scalability issues, but that problem can be addressed closer to that time. Many scalability issues can be solved by better hardware such as NVMe disk drives or SSDs and the like. Paying for a costly DB that might solve problems that might happen in 3-4 years depending on design decisions and hardware along with the current constant workarounds that are required for Oracle has become a large time sink for the project. Time of the middleware developers can be used best elsewhere instead of trying to figure out why it works for other DBs and not for Oracle.
Since the Butler/Gen3 environment is not using the consolidated DB with real data and the rest of the project is basically using SQLite, this is a perfect time to move to a different DB before Oracle gets set in stone requiring a transition plan to move to a different DB . The Postgres database has always been tested along side of the Oracle consolidated DB for all Butler/G3 processes and is a natural DB to use due to its open nature, and it is well-supported on many platforms. The hardware already dedicated to the Oracle platform at the LDF can be moved easily to Postgres, and this saves the project from having to purchase the Oracle scaling software called "RAC" each year.
Please leave comments here if you think that the choice of moving to Postgres over Oracle will affect the project in any way negatively.