Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 32E3047612C for ; Mon, 18 Nov 2002 14:14:50 -0500 (EST) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id C1BB1476127 for ; Mon, 18 Nov 2002 14:14:49 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id A8FA243AC2F; Mon, 18 Nov 2002 14:14:49 -0500 (EST) From: taich@gmx.at (Thomas Aichinger) X-Newsgroups: comp.databases.postgresql.questions Subject: Bug with sequence Date: 18 Nov 2002 07:45:19 -0800 Organization: http://groups.google.com/ Lines: 21 Message-ID: <92c0776e.0211180745.49911131@posting.google.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-general@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/793 X-Sequence-Number: 33214 Hi, I recently installed pg 7.2.3 on my linux box and discovered that there are some problems with datatype serial and sequence. 1.) If you create a table with a datatype serial, the corrsponding sequence will be created, but if you drop the table the sequence is not dropped. 2.) If you create a sequence and grant it to public one cant use currval() until one used setval() or nextval(). "ERROR: midnr.currval is not yet defined in this session" 3.) Sometimes one gets 'not enogh privileges' error when using nexval() Am I the first one who discovered that? Thanks Thomas