Re: regression test failures in CVS HEAD

From: Rod Taylor <rbt(at)zort(dot)ca>
To: Neil Conway <neilc(at)samurai(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: regression test failures in CVS HEAD
Date: 2002-08-20 12:05:45
Message-ID: 1029845146.86008.30.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Looks like the expected files weren't updated.

Probably my fault, but the tests themselves are fine.

On Tue, 2002-08-20 at 01:37, Neil Conway wrote:
> The 'type_sanity' and 'domain' regression tests seem to fail with CVS
> HEAD. Here's the diff:
>
> *** ./expected/type_sanity.out Sun Aug 4 15:48:11 2002
> --- ./results/type_sanity.out Tue Aug 20 01:32:35 2002
> ***************
> *** 16,22 ****
> SELECT p1.oid, p1.typname
> FROM pg_type as p1
> WHERE (p1.typlen <= 0 AND p1.typlen != -1) OR
> ! (p1.typtype != 'b' AND p1.typtype != 'c' AND p1.typtype != 'p') OR
> NOT p1.typisdefined OR
> (p1.typalign != 'c' AND p1.typalign != 's' AND
> p1.typalign != 'i' AND p1.typalign != 'd') OR
> --- 16,22 ----
> SELECT p1.oid, p1.typname
> FROM pg_type as p1
> WHERE (p1.typlen <= 0 AND p1.typlen != -1) OR
> ! p1.typtype not in('b', 'c', 'd', 'p') OR
> NOT p1.typisdefined OR
> (p1.typalign != 'c' AND p1.typalign != 's' AND
> p1.typalign != 'i' AND p1.typalign != 'd') OR
> ***************
> *** 60,66 ****
> -- NOTE: as of 7.3, this check finds SET, smgr, and unknown.
> SELECT p1.oid, p1.typname
> FROM pg_type as p1
> ! WHERE p1.typtype = 'b' AND p1.typname NOT LIKE '\\_%' AND NOT EXISTS
> (SELECT 1 FROM pg_type as p2
> WHERE p2.typname = ('_' || p1.typname)::name AND
> p2.typelem = p1.oid);
> --- 60,66 ----
> -- NOTE: as of 7.3, this check finds SET, smgr, and unknown.
> SELECT p1.oid, p1.typname
> FROM pg_type as p1
> ! WHERE p1.typtype in ('b','d') AND p1.typname NOT LIKE '\\_%' AND NOT EXISTS
> (SELECT 1 FROM pg_type as p2
> WHERE p2.typname = ('_' || p1.typname)::name AND
> p2.typelem = p1.oid);
>
> ======================================================================
>
> *** ./expected/domain.out Fri Jul 12 14:43:19 2002
> --- ./results/domain.out Tue Aug 20 01:32:57 2002
> ***************
> *** 143,154 ****
> ( col1 ddef1
> , col2 ddef2
> , col3 ddef3
> ! , col4 ddef4
> , col5 ddef1 NOT NULL DEFAULT NULL
> , col6 ddef2 DEFAULT '88'
> , col7 ddef4 DEFAULT 8000
> , col8 ddef5
> );
> insert into defaulttest default values;
> insert into defaulttest default values;
> insert into defaulttest default values;
> --- 143,155 ----
> ( col1 ddef1
> , col2 ddef2
> , col3 ddef3
> ! , col4 ddef4 PRIMARY KEY
> , col5 ddef1 NOT NULL DEFAULT NULL
> , col6 ddef2 DEFAULT '88'
> , col7 ddef4 DEFAULT 8000
> , col8 ddef5
> );
> + NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'defaulttest_pkey' for table 'defaulttest'
> insert into defaulttest default values;
> insert into defaulttest default values;
> insert into defaulttest default values;
>
> ======================================================================
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2002-08-20 12:22:52 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Previous Message Nigel J. Andrews 2002-08-20 11:59:22 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in