NOTICE: _outNode: don't know how to print type 715

Hi all,

PostgreSQL gives me a strange message when I try to create a table
with a NOT NULL column.

drop table prova;
DROP
create table prova(
campo1 INTEGER
);
CREATE

drop table prova;
DROP
create table prova(
campo1 INTEGER NOT NULL
);
NOTICE: _outNode: don't know how to print type 715
CREATE
\d prova

Table = prova

+---------------------------+----------------------------------+-------+
| Field | Type |
Length|

+---------------------------+----------------------------------+-------+
| campo1 | int4 not null | 4
|

+---------------------------+----------------------------------+-------+

Does someone knows what this message means ?

Thank you,
Jose'

Hi all,

PostgreSQL gives me a strange message when I try to create a table
with a NOT NULL column.

drop table prova;
DROP
create table prova(
campo1 INTEGER
);
CREATE

drop table prova;
DROP
create table prova(
campo1 INTEGER NOT NULL
);
NOTICE: _outNode: don't know how to print type 715
CREATE
\d prova

Table = prova

+---------------------------+----------------------------------+-------+
| Field | Type |
Length|

+---------------------------+----------------------------------+-------+
| campo1 | int4 not null | 4
|

+---------------------------+----------------------------------+-------+

Does someone knows what this message means ?

It is a bug, though I am not sure what is causing it. What version are
you running?

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
http://www.op.net/~candle              |  (610) 353-9879(w)
  +  If your life is a hard drive,     |  (610) 853-3000(h)
  +  Christ can be your backup.        |

Hi all,

PostgreSQL gives me a strange message when I try to create a table
with a NOT NULL column.

drop table prova;
DROP
create table prova(
campo1 INTEGER
);
CREATE

drop table prova;
DROP
create table prova(
campo1 INTEGER NOT NULL
);
NOTICE: _outNode: don't know how to print type 715
CREATE
\d prova

Table = prova

+---------------------------+----------------------------------+-------+
| Field | Type |
Length|

+---------------------------+----------------------------------+-------+
| campo1 | int4 not null | 4
|

+---------------------------+----------------------------------+-------+

Does someone knows what this message means ?

I retract my comment that this is a bug. I can not reproduce this here.

Perhaps your system tables have gotten messed up somehow.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
http://www.op.net/~candle              |  (610) 353-9879(w)
  +  If your life is a hard drive,     |  (610) 853-3000(h)
  +  Christ can be your backup.        |

PostgreSQL gives me a strange message when I try to create a table
with a NOT NULL column.
create table prova(
campo1 INTEGER NOT NULL
);
NOTICE: _outNode: don't know how to print type 715
Does someone knows what this message means ?

I retract my comment that this is a bug. I can not reproduce this
here.

You have compiled the parser subdirectory with -DPARSEDEBUG, which then
tries to print the parse tree. The nodes subdirectory must be compiled
with -DPARSEDEBUG to get extra nodes to be recognized by the printing
routine.

It could be something else, but I get a similar symptom when I do this.

It's my fault that those PARSEDEBUG blocks are in there in the first
place. But I didn't want these nodes which don't usually propagate past
the parser to be mixed in to normal backend nodes in the print routines.

- Tom

Thomas G. Lockhart wrote:

PostgreSQL gives me a strange message when I try to create a table
with a NOT NULL column.
create table prova(
campo1 INTEGER NOT NULL
);
NOTICE: _outNode: don't know how to print type 715
Does someone knows what this message means ?

I retract my comment that this is a bug. I can not reproduce this
here.

You have compiled the parser subdirectory with -DPARSEDEBUG, which then
tries to print the parse tree. The nodes subdirectory must be compiled
with -DPARSEDEBUG to get extra nodes to be recognized by the printing
routine.

It could be something else, but I get a similar symptom when I do this.

You are right Tom, now I remember, the other day I ran the postmaster
with
parameter -d to have debug information about another problem.
Now without -d the bad message is gone away.

Thanks a lot
Jose'