Re: parallel regression test failure - Mailing list pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I think you need a dual cpu machine to see the failures.
> 
> I was wondering about that myself, but we shouldn't fixate on that
> assumption without more evidence.  There could be some other factor
> explaining why I can't reproduce it.  A couple of questions for both
> of you:
>   - what configure options are you using?
>   - can you reproduce the problem with serial tests (make installcheck)?
>   - exactly how repeatable is it --- when it fails, is it always at the
>     same places, or do the failures move around?
> 
> It would also be good to find out exactly where the failures are coming
> from.  Please try running the tests with LOG_ERROR_VERBOSITY set to
> VERBOSE (probably the easiest way to hack this in make check's temp
> installation is to modify src/backend/utils/misc/postgresql.conf.sample).
> Then the postmaster log file created by make check will show the elog
> calls' locations.

OK, I got a failure with verbose output.  Error was:

*** ./expected/triggers.out    Fri Jul 25 12:38:34 2003
--- ./results/triggers.out    Sat Jul 26 12:52:02 2003
***************
*** 66,71 ****
--- 66,72 ---- ERROR:  tuple references non-existent key DETAIL:  Trigger "check_fkeys2_pkey_exist" found tuple
referencingnon-existent key in "pkeys". insert into fkeys values (10, '1', 2);
 
+ ERROR:  could not open relation with OID 119980 insert into fkeys values (30, '3', 3); insert into fkeys values (40,
'4',2); insert into fkeys values (50, '5', 2);
 
***************
*** 87,93 **** NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted ERROR:  "check_fkeys2_fkey_restrict":
tupleis referenced in "fkeys" update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 10 and pkey2 = '1';
 
! NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of
fkeys2are deleted DROP TABLE pkeys; DROP TABLE fkeys;
 
--- 88,94 ---- NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted ERROR:  "check_fkeys2_fkey_restrict":
tupleis referenced in "fkeys" update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 10 and pkey2 = '1';
 
! NOTICE:  check_pkeys_fkey_cascade: 0 tuple(s) of fkeys are deleted NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of
fkeys2are deleted DROP TABLE pkeys; DROP TABLE fkeys;
 

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

and logs show:

ERROR:  23514: new row for relation "check_tbl" violates CHECK
constraint "check_con"
LOCATION:  ExecConstraints, execMain.c:1698
ERROR:  09000: tuple references non-existent key
DETAIL:  Trigger "check_fkeys2_pkey_exist" found tuple referencing
non-existent key in "pkeys".
LOCATION:  check_primary_key, refint.c:214
ERROR:  23514: new row for relation "check_tbl" violates CHECK
constraint "check_con"
LOCATION:  ExecConstraints, execMain.c:1698

ERROR:  XX000: could not open relation with OID 119980
LOCATION:  relation_open, heapam.c:459

ERROR:  23502: null value for attribute "aa" violates NOT NULL
constraint
LOCATION:  ExecConstraints, execMain.c:1686
ERROR:  09000: tuple references non-existent key

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073