If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the problem but solved it and generated a patch
then e-mail it to [EMAIL PROTECTED] instead. Please use the
command "diff -c" to generate the patch.
You may also enter a bug report at http://www.postgresql.org/ instead of
e-mail-ing this form.
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Bill Studenmund
Your email address : [EMAIL PROTECTED]
System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel Pentium
Operating System (example: Linux 2.0.26 ELF) : NetBSD 1.5.2
PostgreSQL version (example: PostgreSQL-7.1.1): PostgreSQL-7.2devel
Compiler used (example: gcc 2.95.2) :
Please enter a FULL description of your problem:
------------------------------------------------
Enabling --debug while running regression tests notes regression test
failures which are not present when --debug is not enabled.
The foreign_key test fails, when it succeeds w/o --debug. I've attached
the output of regression.diff.
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
cd src/tests/regression; gmake check; Apply the patch to GNUmakefile I've
attached and gmake check. Note that the foreign_key test fails.
Node type 725 is, according to include/nodes/nodes.h, T_FkConstraint.
Probably what happened was that when tgl added the node type (revision
1.68 of this file), he didn't add a T_FkConstraint clause to
backend/nodes/outfuncs.c:_outNode(). There will probably also need to be a
way for the output to be read back in.
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
src/backend/nodes/outfuncs.c:_outNode() needs to be able to dump a foreign
key contraint. Also an FK constraint will need to be parsed when the plan
is read back in.
Index: GNUmakefile
===================================================================
RCS file: /projects/cvsroot/pgsql/src/test/regress/GNUmakefile,v
retrieving revision 1.35
diff -u -r1.35 GNUmakefile
--- GNUmakefile 2001/09/16 16:11:11 1.35
+++ GNUmakefile 2001/10/24 00:09:48
@@ -110,7 +110,7 @@
##
check: all
- $(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir)
--schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE)
+ $(SHELL) ./pg_regress --temp-install --top-builddir=$(top_builddir)
+--schedule=$(srcdir)/parallel_schedule --multibyte=$(MULTIBYTE) --debug
installcheck: all
$(SHELL) ./pg_regress --schedule=$(srcdir)/serial_schedule
--multibyte=$(MULTIBYTE)
*** ./expected/foreign_key.out Thu Oct 11 17:07:15 2001
--- ./results/foreign_key.out Tue Oct 23 14:45:41 2001
***************
*** 9,14 ****
--- 9,16 ----
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 725
+ NOTICE: _outNode: don't know how to print type 725
-- Insert test data into PKTABLE
INSERT INTO PKTABLE VALUES (1, 'Test1');
INSERT INTO PKTABLE VALUES (2, 'Test2');
***************
*** 233,238 ****
--- 235,242 ----
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 725
+ NOTICE: _outNode: don't know how to print type 725
-- Insert test data into PKTABLE
INSERT INTO PKTABLE VALUES (1, 'Test1');
INSERT INTO PKTABLE VALUES (2, 'Test2');
***************
*** 733,744 ****
--- 737,752 ----
-- because varchar=int does exist
CREATE TABLE FKTABLE (ftest1 varchar REFERENCES pktable);
NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
+ NOTICE: _outNode: don't know how to print type 725
+ NOTICE: _outNode: don't know how to print type 725
DROP TABLE FKTABLE;
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table
"pktable"
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table
"pktable"
-- As should this
CREATE TABLE FKTABLE (ftest1 varchar REFERENCES pktable(ptest1));
NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
+ NOTICE: _outNode: don't know how to print type 725
+ NOTICE: _outNode: don't know how to print type 725
DROP TABLE FKTABLE;
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table
"pktable"
NOTICE: DROP TABLE implicitly drops referential integrity trigger from table
"pktable"
***************
*** 827,832 ****
--- 835,842 ----
NOTICE: CREATE TABLE/UNIQUE will create implicit index 'pktable_base1_key' for
table 'pktable'
create table fktable (ftest1 int references pktable(base1));
NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
+ NOTICE: _outNode: don't know how to print type 725
+ NOTICE: _outNode: don't know how to print type 725
-- now some ins, upd, del
insert into pktable(base1) values (1);
insert into pktable(base1) values (2);
======================================================================
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
