major failures in regression tests

Hi Folks,

I've been trying to get Postgres operational on my machine. It seems to
build ok, and some of the regression tests run successfully, but some of
the tests fail miserably.

Here are some details

Configuration:

Postgres 6.5.3 - no patches, changes, etc. to source tree

Solaris 2.6 on SPARC (Sun 4m)
-- added set shmsys:shminfo_shmmax=0x7fffffff to /etc/system

ran configure with the following options:
--with-tcl
--with-perl
--with-odbc
--enable-locale
--enable-cassert

built cleanly

note: config.cache is attached

----
test results (regress.out, with annotation):

note: regression.diffs is attached for details

[9:37pm]# more regress.out
awk: syntax error near line 1
awk: illegal statement near line 1
=============== Notes... =================
postmaster must already be running for the regression tests to succeed.
The time zone is now set to PST8PDT explicitly by this regression test
client frontend. Please report any apparent problems to
ports(at)postgresql(dot)org
See regress/README for more information.

=============== destroying old regression database... =================
ERROR: destroydb: database 'regression' does not exist
destroydb: database destroy failed on regression.
=============== creating new regression database... =================
=============== installing PL/pgSQL... =================
=============== running regression queries... =================
boolean .. ok
char .. ok
name .. ok
varchar .. ok
text .. ok
strings .. ok
int2 .. failed - looks ok (minor message change shows in diff file)
int4 .. failed - looks ok (minor message change shows in diff file)
int8 .. ok
oid .. ok
float4 .. ok
float8 .. ok
numerology .. ok
point .. ok
lseg .. ok
box .. ok
path .. ok
polygon .. ok
circle .. ok
geometry .. failed - looks ok (diffs in least significant digits)
timespan .. ok
datetime .. ok
reltime .. ok
abstime .. failed - looks ok (PST vs. PDT in a few places)
tinterval .. failed - looks ok (PST vs. PDT in a few places)
horology .. failed - looks ok (PST vs. PDT in a few places)
inet .. ok
comments .. ok
oidjoins .. ok
type_sanity .. ok
opr_sanity .. ok
create_function_1 .. ok
create_type .. ok
create_table .. ok
create_function_2 .. failed - looks serious - file wouldn't load
constraints .. ok
triggers .. failed - looks serious - filed wouldn't load
copy .. ok
create_misc .. ok
create_aggregate .. ok
create_operator .. ok
create_view .. ok
create_index .. ok
sanity_check .. ok
errors .. ok
select .. ok
select_into .. ok
select_distinct .. ok
select_distinct_on .. ok
select_implicit .. ok
select_having .. ok
subselect .. ok
union .. ok
case .. ok
join .. ok
aggregates .. ok
transactions .. ok
random .. failed - as expected
portals .. ok
misc .. failed - file wouldn't load
arrays .. ok
btree_index .. ok
hash_index .. ok
select_views .. ok
alter_table .. ok
portals_p2 .. ok
rules .. ok
limit .. ok
plpgsql .. Bus Error - failed - this one looks serious
temp .. ok
numeric .. failed - loaded lots of data, but queries all resulted in
empty results, test process hung, had to abort at this point

I hope this is useful.

Miles Fidelman

**************************************************************************
Network Technology Corporation PO Box 600618
Miles R. Fidelman, President Newtonville, MA 02460-0006
mfidelman(at)ntcorp(dot)com 617-558-3698
http://www.ntcorp.com fax: 617-630-8946
**************************************************************************