Bug? Re: select following an insert fails in getTypeInfo()

Hi,

   in regards to my last mail I've found the problem. If I turn on verbose
debugging in the postgres server then pypgsql barfs here:

Line 866 in /usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py

            if len(self.__conn.notices) != _nl:
                raise Warning, self.__conn.notices.pop()

It seems that the extra debug information has found it's way into the 
self.__conn.notices
and is being treated as an error!

Even if I catch this warning this will stop the function from completing 
so the library
continues not to work. I can remove this problem for me by disabling the 
extra logging in
/etc/postgresql/postgresql.conf

log_statement = true

will break it on a select for me. If i turn that off it'll break with 
debug info in notices at a later
stage. It looks like all (or at least a lot of) the debug info is making 
it into notices and being
considered an error.

If this is normal and configurable to off then sorry for the post. I 
could find no documentation on
this and it looks like a bug, or a confusing default behaviour at least.

    Greg



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642