pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Lemon <Jim.Lemon@uts.EDU.AU>
To: pgsql-interfaces@hub.org
Subject: Problem with regression test
Date: Tue, 29 Jun 1999 21:59:10 +0000
Message-ID: <377941AD.4CB0543E@uts.edu.au> (raw)

My apologies if this is the wrong list - my message was bounced from the
address in the documentation.

Hi,

Tried to set up postgreSQL v6.5 on a:

486DX66
32Mb RAM
4.3 Gb HDD  (less than 1Gb used)
RedHat Linux 5.2 (2.0.36)

Uncompressing the file left me with a 'postgresql-6.5' directory which
had to be included in the path (this isn't shown in the instructions).
Make succeeded, and I was able to run the 'createdb' example in the
instructions.
Regression test failed at this point:

...
select_views .. ok
alter_table .. ERROR:  Unable to locate type name 'dt' in catalog
ERROR:  Relation 'tmp' does not have attribute 'k'
ERROR:  Unable to locate type name 'dt' in catalog
ERROR:  Relation 'tmp' does not have attribute 'k'
ok
portals_p2 .. ok
rules .. failed
limit .. ok
plpgsql .. ERROR:  Cannot insert a duplicate key into a unique index
ERROR:  WS.not.there         does not exists
ERROR:  illegal backlink beginning with XX
ERROR:  PS.not.there         does not exists
ERROR:  illegal slotlink beginning with XX
ERROR:  Cannot insert a duplicate key into a unique index
ERROR:  no manual manipulation of HSlot
ERROR:  no manual manipulation of HSlot
ERROR:  system "notthere" does not exist
ERROR:  IFace slotname "IF.orion.ethernet_interface_name_too_long" too
long (20 char max)
ok
temp .. ERROR:  temptest: Table does not exist.
ok
numeric .. DEBUG:  --Relation num_exp_add--
DEBUG:  Pages 2: Changed 0, Reapped 0, Empty 0, New 0; Tup 100: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 50, MaxLen 118; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_add_idx: Pages 2; Tuples 100. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_sub--
DEBUG:  Pages 2: Changed 0, Reapped 0, Empty 0, New 0; Tup 100: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 50, MaxLen 119; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_sub_idx: Pages 2; Tuples 100. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_div--
DEBUG:  Pages 2: Changed 0, Reapped 0, Empty 0, New 0; Tup 100: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 50, MaxLen 118; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_div_idx: Pages 2; Tuples 100. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_mul--
DEBUG:  Pages 2: Changed 0, Reapped 0, Empty 0, New 0; Tup 100: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 50, MaxLen 137; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_mul_idx: Pages 2; Tuples 100. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_sqrt--
DEBUG:  Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 10: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 46, MaxLen 106; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_sqrt_idx: Pages 2; Tuples 10. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_ln--
DEBUG:  Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 10: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 46, MaxLen 97; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_ln_idx: Pages 2; Tuples 10. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_log10--
DEBUG:  Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 10: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 46, MaxLen 97; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_log10_idx: Pages 2; Tuples 10. Elapsed 0/0 sec.
DEBUG:  --Relation num_exp_power_10_ln--
DEBUG:  Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 10: Vac 0,
Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 46, MaxLen 139; Re-using:
Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
DEBUG:  Index num_exp_power_10_ln_idx: Pages 2; Tuples 10. Elapsed 0/0
sec.

at this point, the program apparently hung (using over 90% CPU) for
several minutes, until I killed the 'regression' process as root.  The
xterm then displayed:

failed
ACTUAL RESULTS OF REGRESSION TEST ARE NOW IN FILE regress.out
...

I can still run commands like 'createdb', etc.

Hopefully, this is a simple-minded error on my part.  Thanks for any
help you can offer.

Jim




view thread (4+ messages)  latest in thread

Message-ID: <377941AD.4CB0543E@uts.edu.au>
Permalink:  ../377941AD.4CB0543E@uts.edu.au/
Also on:    postgresql.org/message-id/377941AD.4CB0543E@uts.edu.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: Jim.Lemon@uts.EDU.AU, pgsql-interfaces@hub.org
  Subject: Re: Problem with regression test
  In-Reply-To: <377941AD.4CB0543E@uts.edu.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox