Enabling --debug causes regression test failure.

Started by Bill Studenmundover 24 years ago3 messagesbugs
Jump to latest
#1Bill Studenmund
wrstuden@netbsd.org

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 pgsql-ports@postgresql.org.

To report any other bug, fill out the form below and e-mail it to
pgsql-bugs@postgresql.org.

If you not only found the problem but solved it and generated a patch
then e-mail it to pgsql-patches@postgresql.org 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 : wrstuden@netbsd.org

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.

Attachments:

reg.diffstext/plain; charset=US-ASCII; name=reg.diffsDownload+1-1
regression.diffstext/plain; charset=US-ASCII; name=regression.diffsDownload+10-0
#2Bill Studenmund
wrstuden@netbsd.org
In reply to: Bill Studenmund (#1)
Re: Enabling --debug causes regression test failure.

On Thu, 25 Oct 2001, Tom Lane wrote:

Bill Studenmund <wrstuden@netbsd.org> writes:

Enabling --debug while running regression tests notes regression test
failures which are not present when --debug is not enabled.

Not --enable-debug, but running with debug_print_parse turned on.

I've added the missing print routine.

Cool.

Take care,

Bill

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bill Studenmund (#1)
Re: Enabling --debug causes regression test failure.

Bill Studenmund <wrstuden@netbsd.org> writes:

Enabling --debug while running regression tests notes regression test
failures which are not present when --debug is not enabled.

Not --enable-debug, but running with debug_print_parse turned on.

I've added the missing print routine.

regards, tom lane