Re: [ADMIN] how to alter sequence.

From: "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] how to alter sequence.
Date: 2002-12-04 15:51:24
Message-ID: 3DEE71D4.21116.1940487@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 4 Dec 2002 at 20:41, Hannu Krosing wrote:
> hannu=# update seq set max_value = 99;
> ERROR: You can't change sequence relation seq
> hannu=# update pg_class set relkind = 'r' where relname = 'seq';
> UPDATE 1
> hannu=# update seq set max_value = 99;
> UPDATE 1
> hannu=# update pg_class set relkind = 'S' where relname = 'seq';
> UPDATE 1
> hannu=# select * from seq;
> sequence_name | last_value | increment_by | max_value | min_value |
> cache_value | log_cnt | is_cycled | is_called
> ---------------+------------+--------------+-----------+-----------+-------------+---------+-----------+-----------
> seq | 1 | 1 | 99 | 1
> | 1 | 1 | f | f

That makes me wonder. If sequense is treated like a single column single row
table and it's value is guarenteed to be increasing even in case of aborted
transaction, is it correct to say that postgresql already has nested
transactions, albeit dormant?

Bye
Shridhar

--
Zero Defects, n.: The result of shutting down a production line.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Hannu Krosing 2002-12-04 15:57:26 Re: [ADMIN] how to alter sequence.
Previous Message Hannu Krosing 2002-12-04 15:41:59 Re: [HACKERS] how to alter sequence.

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2002-12-04 15:57:26 Re: [ADMIN] how to alter sequence.
Previous Message Hannu Krosing 2002-12-04 15:41:59 Re: [HACKERS] how to alter sequence.