Re: PostgreSQL 8.3.0 'unrecognized node type: 1718580065'

Please, can you provide a test case? Which command does fail?
Thanks Zdenek


Vladimir Kokovic wrote:
> Hi all,
> 
> I am using version 8.3.0 of the source and compiled it with next options:
> 
> PostgreSQL config.status 8.3.0
> configured by ./configure, generated by GNU Autoconf 2.59,
>   with options \"'--enable-cassert' '--enable-debug' '--enable-nls' '--enable-integer-datetimes' '--with-perl'
'--with-python''--with-tcl' '--with-krb5' '--with-openssl' '--enable-thread-safety' '--with-ldap'
'--prefix=/media/hda5/postgresql-8.3.0'\"
> 
> I am on Kubuntu 7.10:
> Linux vladakk-kuci 2.6.22-14-generic #1 SMP Fri Feb 1 04:59:50 UTC 2008 i686 GNU/Linux
> 
> Something is wrong on server side !
> 
> I don't know if this is known bug, but look in my PostgreSQL log file:
> 
> 2008-02-07 17:05:18 CET asoft vlada LOG:  00000: execute <unnamed>: CREATE SCHEMA asoft
> 2008-02-07 17:05:18 CET asoft vlada LOCATION:  exec_execute_message, postgres.c:1820
> 2008-02-07 17:05:18 CET asoft vlada LOG:  00000: duration: 0.806 ms
> 2008-02-07 17:05:18 CET asoft vlada LOCATION:  exec_execute_message, postgres.c:1890
> 2008-02-07 17:05:18 CET asoft vlada ERROR:  XX000: unrecognized node type: 1718580065
> 2008-02-07 17:05:18 CET asoft vlada LOCATION:  copyObject, copyfuncs.c:3573
> 2008-02-07 17:05:18 CET asoft vlada STATEMENT:  ALTER SCHEMA asoft OWNER TO postgres
> 2008-02-07 17:05:18 CET asoft vlada LOG:  08P01: unexpected EOF on client connection
> 2008-02-07 17:05:18 CET asoft vlada LOCATION:  SocketBackend, postgres.c:323
> 2008-02-07 17:05:18 CET asoft vlada LOG:  00000: disconnection: session time: 0:00:05.515 user=vlada database=asoft
host=localhostport=55602
 
> 2008-02-07 17:05:18 CET asoft vlada LOCATION:  log_disconnections, postgres.c:3940
> 
> Best regards,
> Vladimir Kokovic, DP senior, Belgrade, Serbia
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match