Kris Jurka <[EMAIL PROTECTED]> writes:
> On Thu, 18 Oct 2007, Tom Lane wrote:
>> It's not that it gets put in the cache, it's that read_info gets called
>> (setting elm->increment). I think we probably should clean this up by
>> creating a separate flag in that struct that explicitly says "currval
On Thu, 18 Oct 2007, Tom Lane wrote:
Looks like any alter sequence command will do this. The serial case uses
alter sequence owned by under the hood which exposes this. The problem is
that altering the sequence puts it into the SeqTable cache list when it
really shouldn't be.
It's not that
Kris Jurka <[EMAIL PROTECTED]> writes:
>> jurka=# create table t (c serial);
>> NOTICE: CREATE TABLE will create implicit sequence "t_c_seq" for serial
>> column "t.c"
>> CREATE TABLE
>> jurka=# select currval('t_c_seq');
>> currval
>> -
>> 1
>> (1 row)
>>
>> I would expect it to say tha
On Thu, 18 Oct 2007, Kris Jurka wrote:
jurka=# create table t (c serial);
NOTICE: CREATE TABLE will create implicit sequence "t_c_seq" for serial
column "t.c"
CREATE TABLE
jurka=# select currval('t_c_seq');
currval
-
1
(1 row)
I would expect it to say that currval wasn't set
jurka=# create table t (c serial);
NOTICE: CREATE TABLE will create implicit sequence "t_c_seq" for serial
column "t.c"
CREATE TABLE
jurka=# select currval('t_c_seq');
currval
-
1
(1 row)
I would expect it to say that currval wasn't set like so:
jurka=# create sequence myseq;
