Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 54101476656
	for <pgsql-sql@postgresql.org>; Thu, 10 Oct 2002 11:17:22 -0400 (EDT)
Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46])
	by postgresql.org (Postfix) with ESMTP id 6616247660B
	for <pgsql-sql@postgresql.org>; Thu, 10 Oct 2002 11:17:21 -0400 (EDT)
Received: from desktop ([62.252.136.157]) by mta06-svc.ntlworld.com
	(InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP
	id <20021010151725.WWTO28874.mta06-svc.ntlworld.com@desktop>
	for <pgsql-sql@postgresql.org>; Thu, 10 Oct 2002 16:17:25 +0100
Message-ID: <001101c27070$3060bf10$9d88fc3e@desktop>
From: "John Duffy" <jbduffy@ntlworld.com>
To: <pgsql-sql@postgresql.org>
Subject: NOTICE: generated by sequence nextval()
Date: Thu, 10 Oct 2002 16:17:40 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C27078.8E09D270"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200210/136
X-Sequence-Number: 9853

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C27078.8E09D270
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Postgresql 7.1.3-2
Red Hat 7.2

I've noticed that if I create a sequence, and then do a select on it using =
nextval() everything works fine. However, if I drop the sequence and then c=
reate it again, the same select statement generates a NOTICE.

Is this normal behaviour or a bug? See below.

test=3D> create sequence serial;
CREATE
test=3D> select nextval('serial');
 nextval
---------
       1
(1 row)

test=3D> drop sequence serial;
DROP
test=3D> create sequence serial;
CREATE
test=3D> select nextval('serial');
NOTICE:  serial.nextval: sequence was re-created
 nextval
---------
       1
(1 row)=20


------=_NextPart_000_000E_01C27078.8E09D270
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Postgresql 7.1.3-2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Red Hat 7.2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I've noticed that if I create a sequence, =
and then=20
do a select on it using nextval() everything works fine. However, if I drop=
 the=20
sequence and then create it again, the same select statement generates a=20
NOTICE.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is this normal behaviour or a bug? </FONT>=
<FONT=20
face=3DArial size=3D2>See below.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>test=3D&gt; create sequence=20
serial;<BR>CREATE<BR>test=3D&gt; select=20
nextval('serial');<BR>&nbsp;nextval<BR>---------<BR>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
1<BR>(1 row)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>test=3D&gt; drop sequence=20
serial;<BR>DROP<BR>test=3D&gt; create sequence serial;<BR>CREATE<BR>test=3D=
&gt;=20
select nextval('serial');<BR>NOTICE:&nbsp; serial.nextval: sequence was=20
re-created<BR>&nbsp;nextval<BR>---------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
1<BR>(1 row) <BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_000E_01C27078.8E09D270--