Regression tests and NOTICE statements - Mailing list pgsql-hackers

From Rod Taylor
Subject Regression tests and NOTICE statements
Date
Msg-id 28b601c1f6fe$35ff3b90$ad02000a@jester
Whole thread Raw
Responses Re: Regression tests and NOTICE statements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I'm using OIDs for constraint names to guarentee name uniqueness, and
intend to do the same for SERIAL sequences.

The problem with this is that the OID value seems to change with each
run of the regression tests depending on when the last initdb was (in
the case of installcheck) or parallel events in the case of make
check.

There are two solutions that I can see.

One is to make the tests which have data that change in parallel mode
become serial tests (constraints, alter_table and foreign_key).
installcheck will continue to fail if not run immediatly after an
initdb however.

The other is to turn of NOTICE statements for regression tests,
instead displaying only error messages.


For those who are curious, the NOTICE statements in question are
displaying the auto-generated foreign key constraints which table
drops are cascading through.  Implicit drop notices (complex type on a
table) have already been removed.
--
Rod



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: Bad side-effect from making EXPLAIN return a select
Next
From: "Igor Kovalenko"
Date:
Subject: Re: HEADS UP: Win32/OS2/BeOS native ports