Re: porting question: funky uid names?

Mark Bixby wrote:
> It seems that plpgsql.sl didn't get built.  Might be an autoconf issue, since
> quite frequently config scripts don't know about shared libraries on MPE.  I
> will investigate this further.

Ah.  I found src/Makefile.shlib and added the appropriate stuff.

Woohoo!  We have test output!  The regression README was clear about how some
platform dependent errors can be expected, and how to code for these
differences in the expected outputs.

Now I'm off to examine the individual failures....

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
testoid                  ...  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
-- 
mark@bixby.org
Remainder of .sig suppressed to conserve scarce California electrons...