Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 558A5476E3E for ; Thu, 12 Dec 2002 17:52:32 -0500 (EST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.85]) by postgresql.org (Postfix) with ESMTP id 38996476F73 for ; Thu, 12 Dec 2002 17:51:45 -0500 (EST) Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id gBCMplZT018066 for ; Thu, 12 Dec 2002 14:51:47 -0800 (PST) Received: from mac.com ([165.121.130.207]) by asmtp02.mac.com (Netscape Messaging Server 4.15) with ESMTP id H713I900.S49 for ; Thu, 12 Dec 2002 14:51:45 -0800 Date: Thu, 12 Dec 2002 17:50:55 -0500 Subject: PerformPortalClose warning in 7.3 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) From: Michael Engelhart To: pgsql-general@postgresql.org Content-Transfer-Encoding: 7bit In-Reply-To: <3DF91030.A372DF7C@nsd.ca> Message-Id: <2C6CDB6A-0E24-11D7-8E88-000393A48A3C@mac.com> X-Mailer: Apple Mail (2.548) X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/677 X-Sequence-Number: 34592 Hi - I've been running PostgreSQL 7.3 on Mac OS X 10.2 since it was released and it's been running fine. I'm using pyPgSQL 2.3 for client side programming which also was working great until tonight. Now whenever I do any query of any type, I get warnings like this: WARNING: PerformPortalClose: portal "pgsql_00179f10" not found It "appears" that everything is still working the way it was but it's a bit discomforting to have these show up on my screen while running my applications. Anyone that can explain this? Here's a tiny bit of Python sample code that I used to make sure it wasn't my other code causing the problems from pyPgSQL import PgSQL dbname = "template1" conn = PgSQL.connect(database=dbname) cursor = conn.cursor() sql = "SELECT now()"; cursor.execute(sql) res = cursor.fetchall() for i in res: print i cursor.close() conn.commit() strangely if I remove the last 2 lines (cursor.close() and conn.commit()) I don't get the errors. Also I don't notice that I don't have this problem with psql command line either. Is this the Python API causing this? Thanks for any help Mike