Re: using the nextval('sequence_name') in sql, the result maybe is not right

On 9/26/18 5:05 AM, Wanglin wrote: Hi, all:     PostgreSQL version : 10.3.  I use "nextval" in the sql , but I think the result is not right, maybe it is a bug. *The test case as bellow:* create sequence seq1; select nextval('seq1'); create table tx1(id1 int, id2 int); insert into tx1 select

Re: using the nextval('sequence_name') in sql, the result maybe is not right

On Wed, 26 Sep 2018 at 14:08, Wanglin wrote: > > Hi, all: > PostgreSQL version : 10.3. I use "nextval" in the sql , but I think the > result is not right, maybe it is a bug. >The test case as bellow: >create sequence seq1; > select nextval('seq1'); > create table tx1(id1 int, id2

using the nextval('sequence_name') in sql, the result maybe is not right

Hi, all: PostgreSQL version : 10.3. I use "nextval" in the sql , but I think the result is not right, maybe it is a bug. The test case as bellow: create sequence seq1; select nextval('seq1'); create table tx1(id1 int, id2 int); insert into tx1 select generate_series(1,100),