Make check fails on 8.3.7 - Mailing list pgsql-general

From Christine Desmuke
Subject Make check fails on 8.3.7
Date
Msg-id 4A7247FB.8050106@kshs.org
Whole thread Raw
Responses Re: Make check fails on 8.3.7
Re: Make check fails on 8.3.7
List pgsql-general
I'm trying to install 8.3.7, but can't get past make check.

CentOS release 4.7 (Final), with an existing install of 8.3.1 running as
a warm standby

$ eval ./configure `pg_config --configure`
$ gmake
== All of PostgreSQL successfully made. Ready to install.
$ gmake check

Everything looks ok until it actually starts the tests:

./pg_regress --temp-install=./tmp_check --top-builddir=../../..
--srcdir=/home/postgres/postgresql-8.3.7/src/test/regress
--temp-port=55432 --schedule=./parallel_schedule --multibyte=SQL_ASCII
--load-language=plpgsql
============== creating temporary installation        ==============
============== initializing database system           ==============
============== starting postmaster                    ==============
running on port 55432 with pid 16296
============== creating database "regression"         ==============
CREATE DATABASE
ALTER DATABASE
============== installing plpgsql                     ==============
CREATE LANGUAGE
============== running regression test queries        ==============
parallel group (17 tests):  boolean char name varchar text int2 int4 oid
float4 uuid float8 txid money bit int8 enum numeric
      boolean              ... FAILED
      char                 ... FAILED
      name                 ... ok
      varchar              ... FAILED
      text                 ... FAILED
      int2                 ... FAILED
      int4                 ... FAILED
      int8                 ... FAILED
      oid                  ... FAILED
      float4               ... FAILED
      float8               ... FAILED
      bit                  ... FAILED
      numeric              ... FAILED
      txid                 ... FAILED
      uuid                 ... FAILED
      enum                 ... FAILED
      money                ... ok
test strings              ... FAILED
test numerology           ... ok
parallel group (18 tests):  point lseg box path polygon circle time date
tinterval timetz comments reltime abstime tstypes inet interval
timestamptz timestamp
      point                ... FAILED
      lseg                 ... FAILED
      box                  ... FAILED
      path                 ... FAILED
      polygon              ... FAILED
      circle               ... FAILED
      date                 ... FAILED
      time                 ... FAILED
      timetz               ... FAILED
      timestamp            ... FAILED

and so on ...  83 of 114 tests failed.

Samples from the regression.diffs:

*** ./expected/boolean.out      Fri Jun  1 18:40:19 2007
--- ./results/boolean.out       Thu Jul 30 19:16:33 2009
***************
*** 75,83 ****
   (1 row)

   SELECT '  tru e '::text::boolean AS invalid;    -- error
- ERROR:  invalid input syntax for type boolean: "  tru e "
   SELECT ''::text::boolean AS invalid;            -- error
- ERROR:  invalid input syntax for type boolean: ""
   CREATE TABLE BOOLTBL1 (f1 bool);
   INSERT INTO BOOLTBL1 (f1) VALUES (bool 't');
   INSERT INTO BOOLTBL1 (f1) VALUES (bool 'True');
--- 75,81 ----
***************
*** 136,142 ****
   -- For pre-v6.3 this evaluated to false - thomas 1997-10-23
   INSERT INTO BOOLTBL2 (f1)
      VALUES (bool 'XXX');
- ERROR:  invalid input syntax for type boolean: "XXX"
   -- BOOLTBL2 should be full of false's at this point
   SELECT '' AS f_4, BOOLTBL2.* FROM BOOLTBL2;
    f_4 | f1
--- 134,139 ----

======================================================================

*** ./expected/tablespace.out   Thu Jul 30 19:16:15 2009
--- ./results/tablespace.out    Thu Jul 30 19:16:58 2009
***************
*** 48,54 ****
   ALTER INDEX testschema.anindex SET TABLESPACE testspace;
   INSERT INTO testschema.atable VALUES(3);      -- ok
   INSERT INTO testschema.atable VALUES(1);      -- fail (checks index)
- ERROR:  duplicate key value violates unique constraint "anindex"
   SELECT COUNT(*) FROM testschema.atable;               -- checks heap
    count
   -------
--- 48,53 ----
***************
*** 57,69 ****

   -- Will fail with bad path
   CREATE TABLESPACE badspace LOCATION '/no/such/location';
- ERROR:  could not set permissions on directory "/no/such/location": No
such file or directory
   -- No such tablespace
   CREATE TABLE bar (i int) TABLESPACE nosuchspace;
- ERROR:  tablespace "nosuchspace" does not exist
   -- Fail, not empty
   DROP TABLESPACE testspace;
- ERROR:  tablespace "testspace" is not empty
   DROP SCHEMA testschema CASCADE;
   NOTICE:  drop cascades to table testschema.atable
   NOTICE:  drop cascades to table testschema.asexecute
--- 56,65 ----


It looks in every case like the ERROR (and also HINT lines) lines are
causing the failures, but I'm not sure what setting I messed up to cause
that. What should I be looking for?

Thanks.

--

Christine Desmuke
Kansas Historical Society
cdesmuke@kshs.org

pgsql-general by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: pg_config --sharedir points to the wrong folder.. is this a problem?
Next
From: Greg Smith
Date:
Subject: Re: SVN and Postgres 8.3