-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/22/07 07:09, Paul Lambert wrote:
>
> Alban Hertroys wrote:
>> Paul Lambert wrote:
>>
[snip]
> I'd imagine there aren't too many VMS programmers around that
> would be willing to port Postgres either, but if anyone out there
> with experience in VMS wants to give it a go ;) I don't imagine
> it would be an easy task though - not something I'd look forward
> to doing anyway.
These are the categories of organizations running VMS:
1) Companies running a canned app for 15 years on an old, dusty
"late model" (meaning mid-1990s) VAX or old Alpha that just
keeps chugging along. Running a similarly ancient version of
Rdb/VMS or Oracle or Ingres. Or very possibly runs atop the
very rich RMS filesytem layer. (It's how you interact with
files. Gives you simple access to sequential, FORTRAN, DAM &
ISAM files.)
2) Big companies running large SMP systems and relatively recent
versions of Oracle Rdb or Oracle RDBMS, pumping millions of txn
per day.
3) Hobbyists. Greybeards in love with VMS who have one or more
Alphas (and maybe a VAX or two) in their basements, running apps
and compilers with special non-commercial licenses.
4) A variant on #1. Running 5 year old hardware, and probably have
a compiler license. Running Oracle Rdb or Oracle RDBMS.
We are a #2 shop, and when we want a PostgreSQL instance, we don't
run it on OpenVMS (since we need that horsepower for existing work),
but we buy a box from HP and install Linux on it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFtMZYS9HxQb37XmcRAoG4AJsFTyQB7hhoKDz4vM8k5AnKYfT+aQCdFV1F
NW23JKKNDK7Za3pjw3I2fOU=
=FQ/A
-----END PGP SIGNATURE-----