From: | leif(at)crysberg(dot)dk |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Invalid statement name (null) in line ## - what am I doing wrong ? |
Date: | 2009-06-19 01:08:35 |
Message-ID: | 25028798.72981245373715194.JavaMail.root@quick |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I have a problem when upgrading from 8.2.4 to 8.3/8.4 using ecpg with a prepare statement:
EXEC SQL PREPARE execquery FROM :stmt; line = __LINE__;
EXEC SQL AT :_thisDbConn DECLARE execcurs CURSOR FOR execquery; line = __LINE__;
EXEC SQL AT :_thisDbConn OPEN execcurs; line = __LINE__;
EXEC SQL ALLOCATE DESCRIPTOR execdesc; line = __LINE__;
I get an "SQL error: invalid statement name "(null)" on line ##" (3rd line above) on the OPEN cursor statement. I have been digging a little in the ecpg output and noticed that the format of the ECPGprepare() function call has changed between 8.2.4 and 8.3++. Also the ecpg library has changed version libecpg.so.5 -> libecpg.so.6.
I am compiling my program on an (older) system with 8.2.4 installed and I need have my program running on a production system running 8.3.5 or higher. This seems to work fine, but for other reasons I wanted to upgrade my "compile system" with 8.3.5 and this started to give me the error mentioned above.
An ldd on the program gives:
libecpg.so.6 => /usr/local/Packages/pgsql-8.3.5/lib/libecpg.so.6 (0xb7ed8000)
libpq.so.5 => /usr/local/Packages/pgsql-8.3.5/lib/libpq.so.5 (0xb7ebc000)
which looks to be ok. (The 8.2.4 compiled program was using libecpg.so.5.)
It seems to me that somehow the prepare statement (first line above) is compiled into a ECPGprepare() call with 5 parameters, but using a library function with only 3 parameters, even though it points to the libecpg.so.6, which includes code having the 5 parameter ECPGprepare() function.
All PostgreSQL systems are natively installed from source on the various systems, i.e. compiled individually on each system. All my systems are running Linux, but with different versions of Linux.
I have also tried the very newest version 8.4rc1, but with same result, the error above.
Please help,
Leif
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-06-19 01:18:36 | Re: postgresql-8.3.7 unexpected connection closures |
Previous Message | Andrew Maclean | 2009-06-19 00:50:12 | Re: postgresql-8.3.7 unexpected connection closures |