Hi HP3000-L,

Mark Bixby wrote:
> Talk is cheap; actions speak louder than words.  Instead of verbally bemoaning
> the current e3000 database situation, why not take direct personal action to
> change the e3000 world?  Open source gives you this kind of power.
>
> Bixby.org may have more to add to this database thread fairly soon.  Stay
> tuned.  ;-)

BELIEVE IN THE POWER AND THE GLORY OF OPEN SOURCE!  :-)

A new RDBMS lives on the e3000: PostgreSQL (http://www.postgresql.org/).

Starting at about the same time the RDBMS thread appeared on HP3000-L, I began
a port of PostgreSQL that is now largely complete.  The moral of this story is
less whining, more porting, open source changes everything.  ;-)

What follows is the first complete pass of the PostgreSQL test suite.  Some
failures are expected due to platform dependent differences, but others I still
need to investigate:

MULTIBYTE=;export MULTIBYTE; \
/bin/sh ./run_check.sh hppa1.0-hp-mpeix
=============== Removing old ./tmp_check directory ... ================
=============== Create ./tmp_check directory           ================
=============== Installing new build into ./tmp_check  ================
=============== Initializing check database instance   ================
=============== Starting regression postmaster         ================
Regression postmaster is running - PID=125042790 PGPORT=65432
=============== Creating regression database...        ================
CREATE DATABASE
=============== Installing PL/pgSQL...                 ================
=============== Running regression queries...          ================
parallel group1 (12 tests)           ...
 boolean  text  name  oid  float4  varchar  char  int4  int2  float8  int8
nume
ric
           test boolean              ...  ok
           test char                 ...  ok
           test name                 ...  ok
           test varchar              ...  ok
           test text                 ...  ok
           test int2                 ...  ok
           test int4                 ...  ok
           test int8                 ...  ok
           test oid                  ...  ok
           test float4               ...  ok
           test float8               ...  FAILED
           test numeric              ...  ok
sequential test strings              ...  ok
sequential test numerology           ...  ok
parallel group2 (15 tests)           ...
 comments  path  polygon  lseg  point  box  reltime  interval  tinterval
circle
  inet  timestamp  type_sanity  opr_sanity  oidjoins
           test point                ...  ok
           test lseg                 ...  ok
           test box                  ...  ok
           test path                 ...  ok
           test polygon              ...  ok
           test circle               ...  ok
           test interval             ...  FAILED
           test timestamp            ...  FAILED
           test reltime              ...  ok
           test tinterval            ...  ok
           test inet                 ...  ok
           test comments             ...  ok
           test oidjoins             ...  ok
           test type_sanity          ...  ok
           test opr_sanity           ...  ok
sequential test abstime              ...  ok
sequential test geometry             ...  FAILED
sequential test horology             ...  FAILED
sequential test create_function_1    ...  ok
sequential test create_type          ...  ok
sequential test create_table         ...  ok
sequential test create_function_2    ...  ok
sequential test copy                 ...  ok
parallel group3 (6 tests)            ...
 create_aggregate  create_operator  triggers  constraints  create_misc
create_i
ndex
           test constraints          ...  ok
           test triggers             ...  ok
           test create_misc          ...  ok
           test create_aggregate     ...  ok
           test create_operator      ...  ok
           test create_index         ...  ok
sequential test create_view          ...  ok
sequential test sanity_check         ...  ok
sequential test errors               ...  ok
sequential test select               ...  ok
parallel group4 (16 tests)           ...
 arrays  union  select_having  transactions  portals  join  select_implicit
sel
ect_distinct_on  subselect  case  random  select_distinct  select_into
aggregat
es  hash_index  btree_index
           test select_into          ...  ok
           test select_distinct      ...  ok
           test select_distinct_on   ...  ok
           test select_implicit      ...  ok
           test select_having        ...  ok
           test subselect            ...  ok
           test union                ...  ok
           test case                 ...  ok
           test join                 ...  ok
           test aggregates           ...  ok
           test transactions         ...  ok
           test random               ...  ok
           test portals              ...  ok
           test arrays               ...  ok
           test btree_index          ...  ok
           test hash_index           ...  ok
sequential test misc                 ...  ok
parallel group5 (5 tests)            ...
 portals_p2  foreign_key  rules  alter_table  select_views
           test select_views         ...  ok
           test alter_table          ...  ok
           test portals_p2           ...  ok
           test rules                ...  ok
           test foreign_key          ...  ok
parallel group6 (3 tests)            ...
 temp  limit  plpgsql
           test limit                ...  ok
           test plpgsql              ...  FAILED
           test temp                 ...  ok
=============== Terminating regression postmaster      ================
ACTUAL RESULTS OF REGRESSION TEST ARE NOW IN FILES run_check.out
AND regress.out

To run the optional big test(s) too, type 'make bigcheck'
These big tests can take over an hour to complete
These actually are: numeric_big


Now that I've met the challenge of completing this port by the end of the RDBMS
thread ;-), the remaining work will be done at a lower priority on evenings and
weekends.  The test failures need to be investigated, the port needs to be
cleaned up, packaging needs to be done, and documentation needs to be written.
This will probably take a couple of weeks of low priority time.

I expect at least some of you who participated in this HP3000-L thread to step
forward as beta testers.  You now have a new choice in databases for the
e3000.  :-)
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...