[I see on http://www.postgresql.org/docs/admin/install760.htm an invitation to
send info to pgsql-ports@postgreSQL.org but this list is closed for foreign
posters.]
On Friday 18 June 1999, at 14 h 57, the keyboard of "Pedro J. Lobo"
<pjlobo@euitt.upm.es> wrote:
> >Bison seems mandatory (Digital/Compaq's yacc makes errors)
>
> I believe that you can use Compaq's yacc using the '-N' parameter to
> increase the space available to build the LALR tables. I haven't checked
> it, thouth.
Neither did I. I installed bison and everything went fine. This could be
documented.
> Yes, it is very similar to the one I use, except that I don't specify any
> template and I don't enable assertion checking.
Here are y regression tests. I'll study them next week.
=============== 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@postgresql.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
int4 .. failed
int8 .. ok
oid .. ok
float4 .. ok
float8 .. failed
numerology .. ok
point .. ok
lseg .. ok
box .. ok
path .. ok
polygon .. ok
circle .. ok
geometry .. failed
timespan .. ok
datetime .. ok
reltime .. ok
abstime .. failed
tinterval .. failed
horology .. failed
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 .. ok
constraints .. ok
triggers .. ok
copy .. failed
create_misc .. ok
create_aggregate .. ok
create_operator .. ok
create_view .. ok
create_index .. ok
sanity_check .. ok
errors .. ok
select .. failed
select_into .. ok
select_distinct .. failed
select_distinct_on .. failed
select_implicit .. ok
select_having .. ok
subselect .. ok
union .. ok
case .. ok
join .. ok
aggregates .. failed
transactions .. ok
random .. failed
portals .. ok
misc .. failed
arrays .. ok
btree_index .. ok
hash_index .. ok
select_views .. ok
alter_table .. ok
portals_p2 .. failed
rules .. failed
limit .. failed
plpgsql .. ok
temp .. ok
numeric .. ok