sequence last_value not accurate if sequence has never been used - Mailing list pgsql-bugs

From Wayne Schroeder
Subject sequence last_value not accurate if sequence has never been used
Date
Msg-id 20030831230159.GA4457@chewies.net
Whole thread Raw
Responses Re: sequence last_value not accurate if sequence has never been used  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
IMHO, it would be good for the last_value to come back null if is_called
is false.  Don't know if that's possible or even a good idea -- but
figured it was worth a note since the following psql log raised my eye
brow a bit.

Wayne

-------------------------------------
policy=> create sequence a start 1;
CREATE SEQUENCE
policy=> select last_value from a;
 last_value
------------
          1
(1 row)

policy=> select nextval('a');
 nextval
---------
       1
(1 row)

policy=> select last_value from a;
 last_value
------------
          1
(1 row)

policy=> select nextval('a');
 nextval
---------
       2
(1 row)

policy=>
--------------------------------

pgsql-bugs by date:

Previous
From:
Date:
Subject: "Returned due to virus; was:" Re: Your application
Next
From: Tom Lane
Date:
Subject: Re: sequence last_value not accurate if sequence has never been used