Thread: foreign_key regression test fails on Solaris 2.6

foreign_key regression test fails on Solaris 2.6

From
pgsql-bugs@postgresql.org
Date:
Pascal Mueller (pascal@fairware.org) reports a bug with a severity of 4
The lower the number the more severe it is.

Short Description
foreign_key regression test fails on Solaris 2.6

Long Description
Running the regression test on PostgreSQL 7.0.2 on Solaris 2.6 (SPARC)
fails with error message '_outNode: don't know how to print type 726',
see details from the differences file as follows:

*** expected/foreign_key.out    Thu Feb 24 17:02:27 2000
--- results/foreign_key.out     Fri Aug 11 23:44:26 2000
***************
*** 9,14 ****
--- 9,15 ----
  NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable'
  CREATE TABLE FKTABLE ( ftest1 int REFERENCES PKTABLE MATCH FULL ON DELETE CASCADE ON UPDATE CASCADE, ftest2 int );
  NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
+ NOTICE:  _outNode: don't know how to print type 726
  -- Insert test data into PKTABLE
  INSERT INTO PKTABLE VALUES (1, 'Test1');
  INSERT INTO PKTABLE VALUES (2, 'Test2');
***************
*** 233,238 ****
--- 234,240 ----
  NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'pktable_pkey' for table 'pktable'
  CREATE TABLE FKTABLE ( ftest1 int REFERENCES PKTABLE MATCH FULL, ftest2 int );
  NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
+ NOTICE:  _outNode: don't know how to print type 726
  -- Insert test data into PKTABLE
  INSERT INTO PKTABLE VALUES (1, 'Test1');
  INSERT INTO PKTABLE VALUES (2, 'Test2');


Sample Code


No file was uploaded with this report

Re: foreign_key regression test fails on Solaris 2.6

From
Tom Lane
Date:
pgsql-bugs@postgresql.org writes:
> Running the regression test on PostgreSQL 7.0.2 on Solaris 2.6 (SPARC)
> fails with error message '_outNode: don't know how to print type 726',

This is not a platform-specific issue.  Rather, I'll bet you are running
the postmaster with -d set high enough to trigger parsetree dumps into
the postmaster log.  There's some missing code for dumping foreign-key
parsetrees.  It's pretty harmless, really...

            regards, tom lane