Request for IvorySQL Support in pgAdmin 4 to Display Oracle-Compatible Packages

[plopezsoftech]

Dear pgAdmin Development Team,

I hope this message finds you well. My name is Pedro Lopez, and I am a database software developer working with IvorySQL, an open-source PostgreSQL fork that incorporates Oracle compatibility features, such as PL/SQL packages.

I am writing to bring to your attention an issue I've encountered while using pgAdmin 4 (version 9) with IvorySQL (version 4.5). Specifically, pgAdmin does not display the "Packages" node in the browser tree for IvorySQL databases, even though these custom packages exist and can be queried via psql or the Query Tool. From my research, this appears to be because pgAdmin identifies servers as EDB Postgres Advanced Server (which enables the Oracle-compatible UI features) based on keywords like "EnterpriseDB" or "EDB" in the output of "SELECT version();". IvorySQL's version string, however, is formatted as "PostgreSQL 17.5 (IvorySQL 4.5) ...", which pgAdmin treats as standard PostgreSQL, thus hiding these specialized object views.

As a workaround, I have successfully overridden the "version()" function in a custom schema to append "EnterpriseDB" to the output, which tricks pgAdmin into enabling the EDB-compatible display. While this works, it is not ideal for production environments or multi-user setups, as it requires modifying the search_path and could have unintended side effects.

I kindly request that the pgAdmin team consider adding native support for IvorySQL by recognizing keywords like "IvorySQL" in the version string to enable the display of Oracle-compatible features, such as packages. This would greatly enhance usability for users of this PostgreSQL fork and align pgAdmin with emerging database variants that build on PostgreSQL's extensibility.

If this is already on your roadmap or if there are alternative solutions I'm unaware of, I would appreciate any guidance. I can provide more details, logs, or test environments if needed to assist in reproducing the issue.

Thank you for your time and for maintaining such a valuable tool for the PostgreSQL community. I look forward to your response.

Best regards,
Pedro Lopez

[dpage]

Hi,

Unless IvorySQL have copied EDB's proprietary catalogue design for their implementation of Packages and other Oracle compatible features it's unlikely to work as intended, if at all. To provide proper support, IvorySQL would need to be treated as a new database type.

The pgAdmin project welcomes contributions to add support for forks of PostgreSQL as we have for EDB Advanced Server however, we do require that the companies building those products write and maintain the code to do so. If Highgo wish to work on support for IvorySQL we will happily work with them. However, if that maintenance is not sustained over time then we will have to remove support again as we previously did when Pivotal stopped maintaining their Greenplum support for example.