Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D93D8475AE4 for ; Sun, 22 Dec 2002 21:36:30 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 1EF1F4758FE for ; Sun, 22 Dec 2002 21:36:30 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gBN2aRd0028407; Sun, 22 Dec 2002 21:36:27 -0500 (EST) To: Gerhard Haering Cc: pgsql-general@postgresql.org Subject: Re: PerformPortalClose warning in 7.3 In-reply-to: References: <3DF91030.A372DF7C@nsd.ca> <2C6CDB6A-0E24-11D7-8E88-000393A48A3C@mac.com> Comments: In-reply-to Gerhard Haering message dated "Mon, 23 Dec 2002 01:18:46 +0000" Date: Sun, 22 Dec 2002 21:36:27 -0500 Message-ID: <28406.1040610987@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/1064 X-Sequence-Number: 34979 Gerhard Haering writes: > To show this, we use the undocumented, but very handy toggleShowQuery > flag. The effect is that we can see what SQL pyPgSQL sends to the > backend using libpq (the lines staring with QUERY: below): > QUERY: DECLARE "PgSQL_0811F1EC" CURSOR FOR select * from test > ... > QUERY: CLOSE PgSQL_0811F1EC This looks like a pyPgSQL bug to me. If it's going to use a mixed-case name for the cursor then it must either always double-quote the name or never do so. Failing to double-quote in the CLOSE command is wrong. regards, tom lane