Обсуждение: PostgreSql and VMS operating System
With some apologies fpr a third mail on the same day I would like to suggest
postgresql port on VMS if it is not already there.
Going into some background DEC has it's Rdb and both Ingres and Oracle ran
on VMS with VMS initially being the platform of choice at a high expense.
The sudden dot com boom, intel platforms,low end hp and sun servers all lead
to speedy move to Unix.
But I believe Ingres and PostgreSql have lot of commonality probably
there migth be some advantages in runing it on VMS architecture.
If porting was to be attempted I could spend whole lot of time on doing the builds
and testing it on VMS.
Noawadays probbaly VMS might be closer to Unix in pricing than it was in the olden days.
I hope this could be reviewed and someone could let me know if I could join the efforts in anyway.
Sincerely,
Pkv Raju ( Vish Penmetsa)
> On 24 Jan 2025, at 05:29, Vish Penmetsa <vish.penmetsa@gmail.com> wrote: > > With some apologies fpr a third mail on the same day I would like to suggest > postgresql port on VMS if it is not already there. If you are interested in running postgres on OpenVMS you should probably get in touch with https://vmssoftware.com/, they had postgres on their roadmap in the past but I don't see it there anymore. -- Daniel Gustafsson
Probably I might have misunderstood the purpose of the group or the workings of the postgresql group.
I thought the group will look at suggestions on a voluntary basis review them and if found useful will approve to carry forward with the suggestions.
In this case vmssowftare group provides the os copy on VM's but I thought the group leadership will do some communications.
Sincerely,
Pkv Raju
On Fri, Jan 24, 2025 at 1:59 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> On 24 Jan 2025, at 05:29, Vish Penmetsa <vish.penmetsa@gmail.com> wrote:
>
> With some apologies fpr a third mail on the same day I would like to suggest
> postgresql port on VMS if it is not already there.
If you are interested in running postgres on OpenVMS you should probably get in
touch with https://vmssoftware.com/, they had postgres on their roadmap in the
past but I don't see it there anymore.
--
Daniel Gustafsson
> On Jan 24, 2025, at 01:03, Vish Penmetsa <vish.penmetsa@gmail.com> wrote: > > Probably I might have misunderstood the purpose of the group or the workings of the postgresql group. > > I thought the group will look at suggestions on a voluntary basis review them and if found useful will approve to carryforward with the suggestions. > > In this case vmssowftare group provides the os copy on VM's but I thought the group leadership will do some communications. The organization of the PostgreSQL Global Development Group is not like the organization of a commercial software organization. It is up to the general developer community to propose, advocate, and see through any changes (including ports). The "leadership" reviews and approves contributions to the primary core PostgreSQL code, but it is up to the personor organization that wants a feature to do the work to make it actually happen. So, basically, if you want a maintained VMS port, you need to either drive the project yourself, or find others who will. -- 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
On Fri, Jan 24, 2025 at 01:07:56AM -0800, Christophe Pettus wrote: > > > > On Jan 24, 2025, at 01:03, Vish Penmetsa <vish.penmetsa@gmail.com> wrote: > > > > Probably I might have misunderstood the purpose of the group or the workings of the postgresql group. > > > > I thought the group will look at suggestions on a voluntary basis review them and if found useful will approve to carryforward with the suggestions. > > > > In this case vmssowftare group provides the os copy on VM's but I thought the group leadership will do some communications. > > The organization of the PostgreSQL Global Development Group is not like the organization of a commercial software organization. It is up to the general developer community to propose, advocate, and see through any changes (including ports). The "leadership" reviews and approves contributions to the primary core PostgreSQL code, but it is up to the personor organization that wants a feature to do the work to make it actually happen. > > So, basically, if you want a maintained VMS port, you need to either drive the project yourself, or find others who will. This email thread from 2003 says VMS probably doesn't work anymore because of lack of testers: https://www.postgresql.org/message-id/flat/200301071531.h07FVWI08147%40candle.pha.pa.us#0dbc1439f51ec7842125fb8ae200b6da I think we worked on VAX/Unix-Posix for many years after that but we eventually removed it. 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. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
> 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