Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA22487 for ; Wed, 30 Jun 1999 10:07:27 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA21910; Wed, 30 Jun 1999 10:06:10 -0400 (EDT) To: Jim.Lemon@uts.EDU.AU cc: pgsql-interfaces@hub.org Subject: Re: [INTERFACES] Problem with regression test In-reply-to: Your message of Tue, 29 Jun 1999 21:59:10 +0000 <377941AD.4CB0543E@uts.edu.au> Date: Wed, 30 Jun 1999 10:06:10 -0400 Message-ID: <21908.930751570@sss.pgh.pa.us> From: Tom Lane Jim Lemon writes: > 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 These "ERROR" messages are in fact normal log output during the regression test ... but they shouldn't be appearing on your screen! I think that when you started the postmaster, you forgot to redirect its stdout and stderr into a log file per the instructions. The regression tests will usually generate something like 50K of log output (since they deliberately provoke a lot of errors...) > rules .. failed That's a little more disturbing, but you'll need to look at the regression.diffs output to see if the difference is actually meaningful. I suspect there are still a few queries in the rules test wherein the order in which tuples are displayed is platform-dependent ... don't worry about it if the differences turn out to look like that. > at this point, the program apparently hung (using over 90% CPU) for > several minutes, until I killed the 'regression' process as root. Patience, my boy ... the last 'numeric' test is pretty slow, but it's not hung. regards, tom lane