[Info-vax] Status of the PostgreSQL port?

[Stephen Hoffman]

On 2015-06-29 17:20:25 +0000, BillPedersen said:

> To make any progress we need to move forward with the tools with have 
> now.  That has become more and more apparent.
> 
> Yes, we need improved resources.  That will help in the future.  But as 
> of now we have developed various tools and workarounds that for the 
> most part work.
> 
> It would be nice to be able to "fix" the CRTL or even experiment with 
> new features but that seems like a long way down the road right now.


Ayup.   We do have to deal with what we have now.

This as the open-source and even the layered product tool-chains 
involved get ever-longer, and the porting and maintenance efforts get 
ever-higher, and the work-arounds ever more gnarly.    VSI has a very 
large pile of work ahead of them.   So too do the folks working on open 
source on OpenVMS, of course.  Getting C11 and other compiler updates, 
and getting more and newer frameworks, and deprecating the old and 
unused and untestable code — maybe eventually get HP to sanction 
open-sourcing some of the less-used pieces of OpenVMS, as who has 
really used the DECtalk RTL or the parallel-port printing driver in a 
recent application, after all? — is the path forward, though.  It won't 
be easy, and it won't be quick.

I very much do understand what you are writing about here, too.   All 
of the OpenVMS open-source I've worked on most recently — around 100KB 
of new source code, plus some source bits ported from BSD to work 
around the lack of common C calls — is itself a work-around for a lack 
of lowercase aliases in some shareable image symbol vectors.    For a 
lack of lower case alias entries in a shareable image options file 
somewhere.   That's a ~100KB work-around, all to make it easier for 
other open-source projects to be ported to OpenVMS.   All due to a lack 
of options file alias entries.

The ported BSD code is probably a one-shot port, too — something I'll 
reuse here and there, but not something that'll be packaged and made 
more generally useful, too.  But I digress.

VSI has a whole lot ahead of them.  Hopefully we'll learn a bit more at 
the bootcamp.



-- 
Pure Personal Opinion | HoffmanLabs LLC