X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 88A22D1B51C for ; Mon, 8 Sep 2003 21:33:11 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 34575-06 for ; Mon, 8 Sep 2003 18:33:03 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 97F27D1B4E6 for ; Mon, 8 Sep 2003 18:33:00 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h88LX2An003634; Mon, 8 Sep 2003 17:33:02 -0400 (EDT) To: cgg007@yahoo.com Cc: pgsql-sql@postgresql.org Subject: Re: undefine currval() In-reply-to: <20030908211254.80421.qmail@web13801.mail.yahoo.com> References: <20030908211254.80421.qmail@web13801.mail.yahoo.com> Comments: In-reply-to Chris Gamache message dated "Mon, 08 Sep 2003 14:12:54 -0700" Date: Mon, 08 Sep 2003 17:33:02 -0400 Message-ID: <3633.1063056782@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/52 X-Sequence-Number: 15030 Chris Gamache writes: > One (theoretical) workaround would be to issue some sort of command to the > back-end database to wipe all values of currval() when a "new" connection is > made. I've done some digging in the system tables and source code, and can't > find an obvious solution. The state involved is in a linked list kept by commands/sequence.c. Such a command would not be difficult to implement, if you could get agreement on the syntax to use. regards, tom lane