From jbduffy@ntlworld.com Thu Oct  10 15:17:22 2002
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--




From Michael.Ansley@intec-telecom-systems.com Fri Oct  11 09:16:25 2002
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 7CD64475F82
	for <pgsql-sql@postgresql.org>; Fri, 11 Oct 2002 05:16:25 -0400 (EDT)
Received: from fileserver004.intecsystems.co.uk (unknown [194.200.14.120])
	by postgresql.org (Postfix) with ESMTP id 315C0475B8D
	for <pgsql-sql@postgresql.org>; Fri, 11 Oct 2002 05:16:23 -0400 (EDT)
Received: from fileserver002.intecsystems.co.uk (unverified) by
	fileserver004.intecsystems.co.uk
	(Content Technologies SMTPRS 4.2.5) with ESMTP id
	<T5ddf4ce0efc0a8002b165@fileserver004.intecsystems.co.uk>;
	Fri, 11 Oct 2002 09:58:36 +0100
Received: by FILESERVER002 with Internet Mail Service (5.5.2650.21)
	id <TA54QBXZ>; Fri, 11 Oct 2002 10:12:14 +0100
Message-ID: <7F124BC48D56D411812500D0B747251401DA448B@FILESERVER002>
From: "Michael Ansley (UK)" <Michael.Ansley@intec-telecom-systems.com>
To: 'John Duffy' <jbduffy@ntlworld.com>, pgsql-sql@postgresql.org
Subject: Re: NOTICE: generated by sequence nextval()
Date: Fri, 11 Oct 2002 10:12:08 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
 boundary="----_=_NextPart_000_01C27106.46AC0EBE"
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200210/138
X-Sequence-Number: 9855

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C27106.46AC0EBE
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C27106.46AC0EBE"

------_=_NextPart_001_01C27106.46AC0EBE
Content-Type: text/plain; charset="iso-8859-1"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I would hope that this is normal, and I can see it being particularly
useful.  We frequently run into problems where databases ahve been
reloaded, and the sequences have not been reset.  And the DBAs are
not going to take notice unless it's shoved in their face.  It's only
a NOTICE, so it shouldn't affect anything.
 
MikeA
 
 

- -----Original Message-----
From: John Duffy [mailto:jbduffy@ntlworld.com]
Sent: 10 October 2002 16:18
To: pgsql-sql@postgresql.org
Subject: [SQL] NOTICE: generated by sequence nextval()


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 create it again, the same select statement
generates a NOTICE.
 
Is this normal behaviour or a bug? See below.
 
test=> create sequence serial;
CREATE
test=> select nextval('serial');
 nextval
- ---------
       1
(1 row)
 
test=> drop sequence serial;
DROP
test=> create sequence serial;
CREATE
test=> select nextval('serial');
NOTICE:  serial.nextval: sequence was re-created
 nextval
- ---------
       1
(1 row) 



-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPaaUlnympNV/C086EQJNgwCg1TmU/dsMr7ul14koMB5l88ecUcQAoNP6
jH1lHILqYCRzfPOTQ9+lq0BA
=DWs5
-----END PGP SIGNATURE-----




This e-mail and any attachments are confidential and may also be privileged and/or copyright 
material of Intec Telecom Systems PLC (or its affiliated companies).  If you are not an 
intended or authorised recipient of this e-mail or have received it in error, please delete 
it immediately and notify the sender by e-mail.  In such a case, reading, reproducing, 
printing or further dissemination of this e-mail is strictly prohibited and may be unlawful. 
Intec Telecom Systems PLC. does not represent or warrant that an attachment hereto is free 
from computer viruses or other defects. The opinions expressed in this e-mail and any 
attachments may be those of the author and are not necessarily those of Intec Telecom 
Systems PLC. 

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.


------_=_NextPart_001_01C27106.46AC0EBE
Content-Type: text/html; charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: [SQL] NOTICE: generated by sequence nextval()</TITLE>
</HEAD>
<BODY>

<P>-----BEGIN PGP SIGNED MESSAGE-----<BR>
Hash: SHA1<BR>
<BR>
I would hope that this is normal, and I can see it being particularly<BR>
useful.&nbsp; We frequently run into problems where databases ahve been<BR>
reloaded, and the sequences have not been reset.&nbsp; And the DBAs are<BR>
not going to take notice unless it's shoved in their face.&nbsp; It's only<BR>
a NOTICE, so it shouldn't affect anything.<BR>
<BR>
MikeA<BR>
<BR>
<BR>
<BR>
- -----Original Message-----<BR>
From: John Duffy [<A HREF="mailto:jbduffy@ntlworld.com">mailto:jbduffy@ntlworld.com</A>]<BR>
Sent: 10 October 2002 16:18<BR>
To: pgsql-sql@postgresql.org<BR>
Subject: [SQL] NOTICE: generated by sequence nextval()<BR>
<BR>
<BR>
Postgresql 7.1.3-2<BR>
Red Hat 7.2<BR>
<BR>
I've noticed that if I create a sequence, and then do a select on it<BR>
using nextval() everything works fine. However, if I drop the<BR>
sequence and then create it again, the same select statement<BR>
generates a NOTICE.<BR>
<BR>
Is this normal behaviour or a bug? See below.<BR>
<BR>
test=&gt; create sequence serial;<BR>
CREATE<BR>
test=&gt; select nextval('serial');<BR>
&nbsp;nextval<BR>
- ---------<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<BR>
(1 row)<BR>
<BR>
test=&gt; drop sequence serial;<BR>
DROP<BR>
test=&gt; create sequence serial;<BR>
CREATE<BR>
test=&gt; select nextval('serial');<BR>
NOTICE:&nbsp; serial.nextval: sequence was re-created<BR>
&nbsp;nextval<BR>
- ---------<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<BR>
(1 row)<BR>
<BR>
<BR>
<BR>
-----BEGIN PGP SIGNATURE-----<BR>
Version: PGPfreeware 7.0.3 for non-commercial use &lt;<A HREF="http://www.pgp.com" TARGET="_blank">http://www.pgp.com</A>&gt;<BR>
<BR>
iQA/AwUBPaaUlnympNV/C086EQJNgwCg1TmU/dsMr7ul14koMB5l88ecUcQAoNP6<BR>
jH1lHILqYCRzfPOTQ9+lq0BA<BR>
=DWs5<BR>
-----END PGP SIGNATURE-----<BR>

</P>

<P><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT>&nbsp;

<CODE><FONT SIZE=3><BR>
<BR>
This e-mail and any attachments are confidential and may also be privileged and/or copyright <BR>
material of Intec Telecom Systems PLC (or its affiliated companies).  If you are not an <BR>
intended or authorised recipient of this e-mail or have received it in error, please delete <BR>
it immediately and notify the sender by e-mail.  In such a case, reading, reproducing, <BR>
printing or further dissemination of this e-mail is strictly prohibited and may be unlawful. <BR>
Intec Telecom Systems PLC. does not represent or warrant that an attachment hereto is free <BR>
from computer viruses or other defects. The opinions expressed in this e-mail and any <BR>
attachments may be those of the author and are not necessarily those of Intec Telecom <BR>
Systems PLC. <BR>
<BR>
This footnote also confirms that this email message has been swept by<BR>
MIMEsweeper for the presence of computer viruses.<BR>
</FONT></CODE>
</BODY>
</HTML>
------_=_NextPart_001_01C27106.46AC0EBE--

------_=_NextPart_000_01C27106.46AC0EBE
Content-Type: application/octet-stream;
	name="PGPexch.rtf.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="PGPexch.rtf.asc"

owHtGc9rI9fZJM0lYQOhUALp4YsDdTbY0sxYsr225UaWtGs1tuWVtQlLZg9v
Zt6MJn56T34zY62zETmGHnpoKaWXEgIht9JCL/kD+hcUAoFCD73lHgK55Xsa
SZbk8a5mjZPdjYZdWfre9/vne29+P7f1/AtzhS/+/JePvvj8q49fqq2/8tw/
/jj36cFr37B/l15e+HrtD59+8sZzt//zq1f+N/fX/177/y/+9taX7nd/+v6X
v/721c/+9eE//76Yt+bU88CUoaubhAd+78Nue7qRN0xXilYzbDEdTIe6rvbA
dAUPQ4tdexG/aqYbdPwgMF27SWRAQw2K0idso9tb1k23JRwqOZREJH0qYZ92
+mvImvtsSGjA4WnLEgPK5QHlCOfzPHIPF5/vL0ODNEWLbHR7YFswIdEAU1JH
Mz1JKddMi0VU2zgHMvL5ZCByMiNbN9tEOmabEZ8r94TEWl7RIPaLkQMl7i1T
uS8knpFbhs3Xy7VS4+5BBXYae7twcGd7t1qC+aVs9r3lUjZbbpTjhVxGg4ZU
cQh9wQnLZiv781vdMX7LoKTDOFC/AZuKwyRuDsGVYnkCrCeySASu6LC5V2kU
wcbwUx4W5vcOe6quZDQtY6zghzYPnLRo4VZlv1IvNmr1aaQZOWR82Li7W9k6
vzAJQeOySbiJnBXjbILRRhJyXoPN7Vr5LlheSeVH4Q2392x1exhYG2Ce+LRz
5HMnH1NaxD7ypIi4Aw/MoNlWMPzj8yDE3/gz4OD6jPX4dfHnCegrq6urhp7v
ds8wbiIKdfrrXfUMJGrj+aMl6X1jBTbL1XdH1HxwRj6Ct5JLxBjjtYZJcnhQ
3AebkSAo6Pm1fE7LaTeWdF3XDE0zth7NQ8+twebN2n4DXGLTQq8awY49quHj
uhD4H9LCOC83B6btYmCwatDMIevqOPNc3wMdETEHmqJNIWySED/8APAfF7JF
2CIQDEkVbMIhoBT8ECzqcw+QNvTtiBHJTpMZRwF1I5aZ9MpvuBW0N0YyYYFo
Z0rCexRcSY8jrApkLCMOPg8FtKWwGG0F0GlSScEh2B1IQAMgzROKKlGerISk
TBCHOrEdYZOiFYq5jaRNgqRchDG5pNjy0mpb7DMtbxdRFRmzS1TEE8praElI
jnpovk0h4oxiR/XDhQCCpjihDlqrGPqyF/K06lQVI8HRcQT2a41qqbKYrE0g
VCRRJMaeL4RAXJfa+IefYvi5Ny5Xz2NdZFUejuTZRYV1w1BtBRM/GXcEc9UY
wpVSZ0jXXhwXr2EpZcfr8lkv654VKWr7yuKVLgFn0b2S6O75R7Q4K8lZSc5K
8rGi+0w4dHu3Vnrn9p1aowKOLwsslP2UDE8ZLcwfFMvl6v6tpd3KzcY65Nv3
N2CvWL9V3R+FbNfq5Uq9DxkkttG+D4FgvjOkqFdv7SCC1r4/P7plR2lKK5SM
38xjpr7ZTUhjiJHDXUpytvQDXItCJsTRHu6LiEd3KG7e5NBgwnyPFxieDcei
fk6jYwZpEs5kvjppPqwjxIfe2CRIbAP5cx1gST016Xs+Hjqhb1EPOC5JV9Gt
j3qa+Zzimfjiitgek22NCL0pRWv9fPZvJ6ce/E40OZQj171gEz8pGYP3fov4
LBTrH1iOonsbN+odIZmTsUXr3hVadohHghSW6RrU7FBYmD6qTUxtnr6yrq9d
oRkNkcKIthccsyX8/3ZbBKGHZ5RjlhHSu0o3R9YHeBZIoeT7h7d37/XPG+tT
+9mjnEoS4pHHOh0eyoDT++EJYW9ev5SFqfEfMZ5/ip7/kFb5uIN1ij4X73wu
2OZM9LeDYUrCakbPLC8ZM6de2ql1LIgdEqJHZ968vDcffxP+RO4Dn3yHVxdO
BrdbTnyf6Lvq+lBSbPVAho0+vo+bdlaETcrBET16pi6qBFf3V1Gg7tSGIwPo
CZXxBRbgjuQoABebfgZ2REetLMaqTCvTkaI9dmE4uEHkA2tQA+IRny/GaKRF
B+oFIa63cL+SehoGw5u7zKz8Z+X/1JV/EL8/iF8egEWb5MQXkQSBhzewIu+3
l4jJmV79Y1hq9Q6pelfARGdWXLPieuocjtMhLJxzpBeOuHHrDHswpYbja9pR
FFCl00baA1WpXik2KmmpUtrUn6/TmjLYGizENi1cT21Vurzty0srZGnwXK12
Pw/s6S960nr7TR2k6FxP1fee4U426+I/RhfvHUN+rB5ertcOrriDT06lJ3na
TO/t3lS6/LTp36GmbHixuExf/PqZbzskmNoGSZfi0DizETkbkZcckU/1bXyM
e/a6dYyk9w70AsL8mqKrle9uTcykVYTvNPZ2J+DLfcd3fwA=

------_=_NextPart_000_01C27106.46AC0EBE--



From thrasher@fibers.upc.es Fri Oct  11 11:20:29 2002
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 7C4B94762EA
	for <pgsql-sql@postgresql.org>; Fri, 11 Oct 2002 07:20:29 -0400 (EDT)
Received: from egwn.net (auth02.nl.egwn.net [193.172.5.4])
	by postgresql.org (Postfix) with ESMTP id 27EFC476164
	for <pgsql-sql@postgresql.org>; Fri, 11 Oct 2002 07:20:26 -0400 (EDT)
Received: from fibers.upc.es (gw01.es3.egwn.net [212.9.66.13]) (authenticated)
	by egwn.net (8.11.6/8.11.6/EGWN) with ESMTP id g9BBJcf18314;
	Fri, 11 Oct 2002 13:19:38 +0200
Message-ID: <3DA6B3CB.5010903@fibers.upc.es>
Date: Fri, 11 Oct 2002 13:19:39 +0200
From: Thrasher <thrasher@fibers.upc.es>
Organization: =?ISO-8859-1?Q?Delegaci=F3_Alumnes_FIB?=
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1b) Gecko/20020721
X-Accept-Language: es-es, en-us
MIME-Version: 1.0
To: "Michael Ansley (UK)" <Michael.Ansley@intec-telecom-systems.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: NOTICE: generated by sequence nextval()
References: <7F124BC48D56D411812500D0B747251401DA448B@FILESERVER002>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200210/139
X-Sequence-Number: 9856

Hi

Just to explain you that I received this email and I am not an intended 
or authorized recipient. So, as you ask, I'm notifying you and deleting 
the mail from my computer.

Thank you


Michael Ansley (UK) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I would hope that this is normal, and I can see it being particularly
> useful.  We frequently run into problems where databases ahve been
> reloaded, and the sequences have not been reset.  And the DBAs are
> not going to take notice unless it's shoved in their face.  It's only
> a NOTICE, so it shouldn't affect anything.
> 
> MikeA
> 
> 
> 
> - -----Original Message-----
> From: John Duffy [mailto:jbduffy@ntlworld.com]
> Sent: 10 October 2002 16:18
> To: pgsql-sql@postgresql.org
> Subject: [SQL] NOTICE: generated by sequence nextval()
> 
> 
> 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 create it again, the same select statement
> generates a NOTICE.
> 
> Is this normal behaviour or a bug? See below.
> 
> test=> create sequence serial;
> CREATE
> test=> select nextval('serial');
>  nextval
> - ---------
>        1
> (1 row)
> 
> test=> drop sequence serial;
> DROP
> test=> create sequence serial;
> CREATE
> test=> select nextval('serial');
> NOTICE:  serial.nextval: sequence was re-created
>  nextval
> - ---------
>        1
> (1 row)
> 
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
> 
> iQA/AwUBPaaUlnympNV/C086EQJNgwCg1TmU/dsMr7ul14koMB5l88ecUcQAoNP6
> jH1lHILqYCRzfPOTQ9+lq0BA
> =DWs5
> -----END PGP SIGNATURE-----
> 
>   |
> 
> This e-mail and any attachments are confidential and may also be 
> privileged and/or copyright
> material of Intec Telecom Systems PLC (or its affiliated companies). If 
> you are not an
> intended or authorised recipient of this e-mail or have received it in 
> error, please delete
> it immediately and notify the sender by e-mail. In such a case, reading, 
> reproducing,
> printing or further dissemination of this e-mail is strictly prohibited 
> and may be unlawful.
> Intec Telecom Systems PLC. does not represent or warrant that an 
> attachment hereto is free
> from computer viruses or other defects. The opinions expressed in this 
> e-mail and any
> attachments may be those of the author and are not necessarily those of 
> Intec Telecom
> Systems PLC.
> 
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> |
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org