Received: from web206.mail.yahoo.com (web206.mail.yahoo.com [128.11.68.106]) by hub.org (8.9.3/8.9.3) with SMTP id QAA98399 for ; Wed, 23 Feb 2000 16:01:40 -0500 (EST) (envelope-from leonbloy@yahoo.com) Received: (qmail 28056 invoked by uid 60001); 23 Feb 2000 21:01:30 -0000 Message-ID: <20000223210130.28055.qmail@web206.mail.yahoo.com> Received: from [200.16.183.3] by web206.mail.yahoo.com; Wed, 23 Feb 2000 13:01:30 PST Date: Wed, 23 Feb 2000 13:01:30 -0800 (PST) From: "Hernan J. Gonzalez" Subject: bug with serial field? To: pgsql-admin@postgreSQL.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii My table 'clientes' has a serial field, with name 'rid'. Now, take a look at these queries: ss => select rid from clientes where rid > 18974 and rid < 18976; rid ----- 18975 (1 row) ss => select rid from clientes where rid = 18975; rid --- (0 rows) A vacuum (or vacuum analyze) did not fix the problem. I only fixed this by droping and recreating the (implicit) index for the sequence: ss => drop index clientes_temp_rid_key; ss => CREATE UNIQUE INDEX "clientes_temp_rid_key" on "clientes" using btree ( "rid" "int4_ops" ); And now, it's ok: ss => select rid from clientes where rid = 18975; rid ----- 18975 (1 row) Rather disturbing, isn't it? Any ideas ? Hernan Gonzalez Buenos Aires, Argentina __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com