Received: from slip1.raccoon.com (slip1.raccoon.com [165.90.135.16]) by hub.org (8.9.2/8.9.1) with ESMTP id JAA19316 for ; Tue, 16 Mar 1999 09:20:08 -0500 (EST) (envelope-from perdue@raccoon.com) Received: from timnt (tim.desmoinesnet.com [165.90.140.11]) by slip1.raccoon.com (8.8.7/8.8.7) with SMTP id IAA14239; Tue, 16 Mar 1999 08:19:03 -0600 Message-ID: <00c601be6fb7$c97d1a30$0b8c5aa5@timnt.weather.net> Reply-To: "Tim Perdue" From: "Tim Perdue" To: "Patrik Kudo" , Subject: Re: [SQL] Setting Next Value in Sequence Date: Tue, 16 Mar 1999 08:17:55 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 That did the trick. Thanks. Tim -----Original Message----- From: Patrik Kudo To: Tim Perdue Cc: pgsql-sql@hub.org Date: Tuesday, March 16, 1999 7:21 AM Subject: Re: [SQL] Setting Next Value in Sequence >Hi, > >You can't manipulate the sequence that way. You can do the following >though: > >select setval('seq_mailid', 1375000); > >Hope that helps. > >Regards, >Patrik Kudo > >Tim Perdue wrote: >> >> Maybe it's due to sleep deprivation, but this is not working. I'm trying to >> update a seqence to a higher number, and it won't let me. >> >> db_domain=> update seq_mailid set last_value=1375000; >> ERROR: You can't change sequence relation seq_mailid >> >> My sense of humor has totally faded over the last two days, and I would >> appreciate sone input. >> >> Tim