Thread: Re: Installing Postegres side-by-side with M$ SQL server]]
Alban Hertroys wrote: > Paul Lambert wrote: > >> G'day folks, >> >> I'm faily new to the world of Postgre so excuse me if these questions seem ignorant. >> >> My current employer develops a software package which runs on OpenVMS on HP Alpha/Itanium servers and contains a custom >> database comprised of various format text and binary files. I.e. not in a real database engine. >> > > >> Having made a decision to port this SQL server database into Postgre I have a few questions before I get started: >> > > I was going to suggest running it on OpenVMS, but apparently it isn't > supported? > (http://www.postgresql.org/docs/8.2/static/supported-platforms.html) > > I only know the name and that it's supposedly rather reliable. Is it > much different from your average UNIX? > > OpenVMS is an extremely reliable and secure operating system... it has a small few similarities to your Unix variants in terms of the interface, but only slight ones. In terms of the programming landscape on a system level, theres almost nothing common between Unix and OpenVMS. I would love a port of Postgres to OpenVMS - but I guess we all have unfulfilled dreams don't we :) 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. Paul.
-----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-----
Ron Johnson wrote: > -----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----- > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > > > We've got pretty new hardware - DS15's, DS25's, Itaniums and so forth. But we don't run any DB app on it, most of our data sits in RMS files or flat binary files - even text files in a few instances, thus making standard DB queries nigh on impossible with the exception of a report generator we've built into the app, but that has nowhere near the capabilities of something like crystal reports or M$ Access, thus the need for a 'replica' standard db model. We looked at Mimer on VMS for a while but threw that out. We've got about 40 Alphas of various power levels and a couple of Itaniums on our WAN so plenty of grunt to spare though. About half of our programming staff would privately fit into category 3 too - myself included (though I did give away my vax a few years ago, leaving me with a solitary DS10) Having said that, I do agree with your point on those main 4 categories of VMS users and thus the unlikelyhood that anyone would be willing to do a Postgres port. Still a shame though :) Paul.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/22/07 14:01, Paul Lambert wrote: > Ron Johnson wrote: On 01/22/07 07:09, Paul Lambert wrote: > >>>> Alban Hertroys wrote: >>>> >>>>> Paul Lambert wrote: >>>>> >>>>> > [snip] > [snip] > We've got pretty new hardware - DS15's, DS25's, Itaniums and so > forth. But we don't run any DB app on it, most of our data sits > in RMS files or flat binary files - even text files in a few > instances, thus making standard DB queries nigh on impossible > with the exception of a report generator we've built into the > app, but that has nowhere near the capabilities of something like > crystal reports or M$ Access, thus the need for a 'replica' > standard db model. We looked at Mimer on VMS for a while but CONNX & Easysoft appear to offer ODBC drivers for (probably only indexed) RMS files, if that helps you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFtSFwS9HxQb37XmcRArreAJ0Y7hxAGemjhMnukvyHGLWDwWy1/QCdHx4t jJoVFkzeucdDivL9QEJXm5k= =uxvA -----END PGP SIGNATURE-----
Ron Johnson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/22/07 14:01, Paul Lambert wrote:
Ron Johnson wrote: On 01/22/07 07:09, Paul Lambert wrote:
Alban Hertroys wrote:
Paul Lambert wrote:
[snip]
[snip]
We've got pretty new hardware - DS15's, DS25's, Itaniums and so
forth. But we don't run any DB app on it, most of our data sits
in RMS files or flat binary files - even text files in a few
instances, thus making standard DB queries nigh on impossible
with the exception of a report generator we've built into the
app, but that has nowhere near the capabilities of something like
crystal reports or M$ Access, thus the need for a 'replica'
standard db model. We looked at Mimer on VMS for a while but
CONNX & Easysoft appear to offer ODBC drivers for (probably only
indexed) RMS files, if that helps you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFtSFwS9HxQb37XmcRArreAJ0Y7hxAGemjhMnukvyHGLWDwWy1/QCdHx4t
jJoVFkzeucdDivL9QEJXm5k=
=uxvA
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
Probably wouldn't - as I said we use a mix of binary, rms (some
indexed, some not) and text files - so an
odbc driver into RMS files would only give us a portion of the
database. A lot of what I replicate to SQL
server at the moment comes from flat binary files and a couple of the
tables from text files, the rest from
RMS files. Having this mix of types would mean we need to manage things
ourselves, thus having our main
in-house faux-database engine forward messages directly to the Weendoze
box which then uses ODBC to
pump the data into the database of my choice. It would make things a
lot easier to manage if I could forward
it to an ODBC database on the VMS machine - oracle is just way out of
our reach though.
Thanks for the suggestion though, that may come in handy down the track
for another project I'm looking at.
P.
--
Paul Lambert
Database Administrator
AutoLedgers
Level 3, 823 Wellington Street, West Perth, W.A. 6005
Postal: P.O. Box 106, West Perth, W.A. 6872
Ph: 08 9217 5086 Fax: 08 9217 5055
AutoLedgers Technical Support Desk: 1800 649 987 (Free call) 08 9217 5050 (Perth local and mobile)
Email: paul.lambert@autoledgers.com.au <http://www.reynolds.com.au>
------------------------------------------------------------------------------------
For AutoLedgers technical support, please send an email to helpdesk@autoledgers.com.au.