Doesn't dropping and recreating the sequence suit the bill ?
whats' the major advantage to implement em as a command?
At least one thing from which all of us can benifit in PgSQL
is replication. I just hope 7.4 give us some sort of master/slave replication.
Regds
Mallah.
On Wednesday 04 December 2002 11:53 pm, Bruce Momjian wrote:
> Oliver Elphick wrote:
> > On Wed, 2002-12-04 at 12:29, raja kumar thatte wrote:
> > > Hai friends,
> > > I have a sequence called raj_seq with max value 3000.
> >
> > ...
> >
> > > now i wanted to increase the max value of the raj_seq
> > > to 9999999.
> > > How to do this change?
> > > If i drop and recreate the raj_seq, then i have to
> > > recreate the table and all triggers working on that
> > > table.But it is not an acceptable solution.
> > > So with out droping raj_seq , how do I solve this
> > > problem.
> >
> > Unfortunately there doesn't seem to be any easy way to do this. There
> > is no ALTER SEQUENCE command and you can't use UPDATE on a sequence.
>
> Gee, I thought they could just update the sequence table, but I see:
>
> test=> update yy set max_value = 100;
> ERROR: You can't change sequence relation yy
>
> > Hackers: Could this be a TODO item for 7.4?
>
> Added to TODO:
>
> * Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values
--
Rajesh Kumar Mallah,
Project Manager (Development)
Infocom Network Limited, New Delhi
phone: +91(11)6152172 (221) (L) ,9811255597 (M)
Visit http://www.trade-india.com ,
India's Leading B2B eMarketplace.