Received: from slip1.raccoon.com (slip1.raccoon.com [165.90.135.16]) by hub.org (8.9.2/8.9.1) with ESMTP id IAA11303 for ; Tue, 16 Mar 1999 08:13:45 -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 HAA13150; Tue, 16 Mar 1999 07:07:12 -0600 Message-ID: <00ad01be6fad$c1097380$0b8c5aa5@timnt.weather.net> Reply-To: "Tim Perdue" From: "Tim Perdue" To: "Remigiusz Sokolowski" , Subject: Re: [SQL] Setting Next Value in Sequence Date: Tue, 16 Mar 1999 07:06:06 -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 May table is defined to use the sequence, and the table is not trivial to export and rebuild with the new sequence. There's got to be some way around this. I'm probably going to have to create a bogus table using that sequence, then insert 150,000 bogus records to increment the sequence. Then drop the table. Tim -----Original Message----- From: Remigiusz Sokolowski To: Tim Perdue Cc: pgsql-sql@hub.org Date: Tuesday, March 16, 1999 6:57 AM Subject: Re: [SQL] Setting Next Value in Sequence >> 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. > >So, may be just drop sequence and create new one with start 1375000. > Rem > >-------------------------------------------------------------------*------- ----- >Remigiusz Sokolowski e-mail: rems@gdansk.sprint.pl * * >-----------------------------------------------------------------*****----- -----