> On Jan 24, 2025, at 08:09, Bruce Momjian <bruce@momjian.us> wrote:
> Our normal development flow is:
>
> https://wiki.postgresql.org/wiki/Todo#Development_Process
> Desirability -> Design -> Implement -> Test -> Review -> Commit
>
> so I would focus on Desirability at this point. The next question is
> whether the demand justifies the code changes.
To expand on this just a bit, you do not need anyone's permission to just take the existing PostgreSQL code base and
getit running on VMS. PostgreSQL is much more truly open-source than a lot of "open source" projects. However, what
youthen have is a fork, rather than the mainline PostgreSQL codebase. Since it is extremely unlikely that you can just
compilethe current code on VMS and have it work, some patches will be required to do conditional compilation and
providesupport code for VMS, and perhaps some additions to and modifications of the documentation and test suite.
The part where you need to negotiate with the community is whether or not to accept those changes back into the
mainline. To be extreme, if the difference is one small conditionally-compiled primitive and the code otherwise runs
justas it did before (including performance) on the currently-supported platforms, the chance is pretty good; if there
isextensive surgery that requires a lot of changes, or if those changes have performance or maintenance impact on the
mainline,the chance is much lower.
--
Christophe Pettus / christophe.pettus@pgexperts.com
Chief Executive Officer / PGX Inc. / 24x7 Support, Consulting, Development / pgexperts.com
See us at: SCaLE, March 6-9, Los Angeles / Nordic PgDay, Copenhagen, March 18
