From: Thrasher <thrasher@fibers.upc.es>
To: Michael Ansley (UK) <Michael.Ansley@intec-telecom-systems.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: NOTICE: generated by sequence nextval()
Date: Fri, 11 Oct 2002 13:19:39 +0200
Message-ID: <3DA6B3CB.5010903@fibers.upc.es> (raw)
References: <7F124BC48D56D411812500D0B747251401DA448B@FILESERVER002>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: thrasher@fibers.upc.es, Michael.Ansley@intec-telecom-systems.com
Subject: Re: NOTICE: generated by sequence nextval()
In-Reply-To: <3DA6B3CB.5010903@fibers.upc.es>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox