[Info-vax] Other than Oracle, What MySQL/DBMS options are there for OpenVms?
John Reagan
xyzzy1959 at gmail.com
Fri Mar 22 16:53:56 EDT 2019
On Friday, March 22, 2019 at 3:16:51 PM UTC-4, Bill Gunshannon wrote:
> On 3/22/19 2:31 PM, Simon Clubley wrote:
> > On 2019-03-22, Bill Gunshannon <bill.gunshannon at gmail.com> wrote:
> >> On 3/21/19 11:04 PM, Stephen Hoffman wrote:
> >>>
> >>>
> >>> Irrespective of what I've seen listed in Wikipedia, PostgreSQL is *not*
> >>> available for OpenVMS,
> >> Just out of curiosity, is there a particular reason for this? Other
> >> than just no one being interested enough to work on a port.
> >>
> >
> > IIRC, there are technical limitations with certain functionality not
> > available on VMS. I think one of the issues was to do with SSIO.
>
> Interesting. I always thought the only real functionality missing
> on VMS was fork(). Too bad, really, because Postgres has got to be
> the best Open Source Database available. If you look at the chart
> on one of the wikis that compares them (except, I think the last
> time I looked it did not include Rdb) Postgres is by far the best
> and most feature loaded DB of any free or commercial.
>
> bill
fork is one of those non-issues that won't die.
In my experience, most uses of "fork" is with a pair of "fork/execv" right in a row. (Think: LIB$SPAWN). For those, replace "fork" with "vfork" or define a macro named "fork" that expands to "vfork". The other uses of "fork" is with ancient code that is doing some sort of poor-man's threading code. Replace those "fork"s with calls to POSIX threads (that could turn into a larger set of changes however) and you'll benefit on all platforms.
More information about the Info-vax
mailing list