Hi there, me again :-)
Whenever I close a connection that holds a prepared statement, the postgres backend logs an error like this:
2008-03-20 09:49:54 CET LOG: execute 1804289383: select user_idnr from dbmail_users where userid=$1 2008-03-20 09:49:54 CET DETAIL: parameters: $1 = 'testuser1' 2008-03-20 09:49:54 CET ERROR: syntax error at or near "1804289383" at character 12 2008-03-20 09:49:54 CET STATEMENT: DEALLOCATE 1804289383;
it's *always* at character 12, where of course the stmt ID varies. It only occurs when I close the connection, I assume because that triggers a Connection_clear, which releases the statements.
This doesn't appear to affect functionality, but it doesn't exactly inspire confidence either, I suppose.
Any ideas?
Thanks for report ... should be fixed ;)
Martin
Paul J Stevens wrote:
Hi there, me again :-)
Whenever I close a connection that holds a prepared statement, the postgres backend logs an error like this:
2008-03-20 09:49:54 CET LOG: execute 1804289383: select user_idnr from dbmail_users where userid=$1 2008-03-20 09:49:54 CET DETAIL: parameters: $1 = 'testuser1' 2008-03-20 09:49:54 CET ERROR: syntax error at or near "1804289383" at character 12 2008-03-20 09:49:54 CET STATEMENT: DEALLOCATE 1804289383;
it's *always* at character 12, where of course the stmt ID varies. It only occurs when I close the connection, I assume because that triggers a Connection_clear, which releases the statements.
This doesn't appear to affect functionality, but it doesn't exactly inspire confidence either, I suppose.
Any ideas?
-
Martin Pala -
Paul J Stevens