Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f01M1dL94989 for ; Mon, 1 Jan 2001 17:01:39 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f01M1HC27717; Mon, 1 Jan 2001 17:01:17 -0500 (EST) To: Ferruccio Zamuner cc: pgsql-sql@postgresql.org Subject: Re: resetting serials and sequences In-reply-to: <200101011548.f01FmZm13200@tnt.diff.org> References: <200101011548.f01FmZm13200@tnt.diff.org> Comments: In-reply-to Ferruccio Zamuner message dated "Mon, 01 Jan 2001 16:48:35 +0100" Date: Mon, 01 Jan 2001 17:01:16 -0500 Message-ID: <27714.978386476@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/5 X-Sequence-Number: 666 Ferruccio Zamuner writes: > Is this a bug? No, but it is a missing feature: there's no way to reset a sequence's is_called flag once it's been set. This is fixed for 7.1: there's now a three-parameter variant of setval() to let you do exactly that. regards, tom lane