pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Henshall, Stuart - WCP <SHenshall@westcountrypublications.co.uk>
To: 'Carolyn Lu Wong' <carolyn@greatpacific.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: weird duplicate data problem
Date: Mon, 17 Dec 2001 15:20:52 -0000
Message-ID: <E2870D8CE1CCD311BAF50008C71EDE8E01F74757@MAIL_EXCHANGE> (raw)



-----Original Message-----
From: Carolyn Lu Wong [mailto:carolyn@greatpacific.com.au]
Sent: 14 December 2001 07:29
To: pgsql-sql@postgresql.org
Subject: weird duplicate data problem


a table was created with:

create table bills (
	id		serial	not null,
	account_no 	int4	not null,
	date_issued	date	not null,
	.....
);

The following SQL script returns only 1 row of data:

	select oid, * from bills where id = xxxxx' order by oid;

--
Seems reasonable
--


However with the following SQL:

	select oid, * from bills where date_issued = '01/01/2001' 
	order by oid;

some of the data is duplicated, including the OID.

--
OIDs are not guaranteed unique and can wraparound (unlesss there's a unique
index). However this seems a little unlikely in the same day so the only
thing I can think of is that there is a corrupt index on date_issued. Try
dropping and recreating any indexes.However I havn't really used 6.5 so
couldn't be sure.
--

When trying to 'vaccum' the database, get

NOTICE:  Index bills_id_key: number of index tupples (4755) is not the
same as heap (7800).

What is happening? What could have caused this?

Database version used is V6.50. I know it's old, but i hope it's not the
version that's causing this problem.

Thanks in advance for any suggestions.



view thread (5+ messages)

Message-ID: <E2870D8CE1CCD311BAF50008C71EDE8E01F74757@MAIL_EXCHANGE>
Permalink:  ../E2870D8CE1CCD311BAF50008C71EDE8E01F74757@MAIL_EXCHANGE/
Also on:    postgresql.org/message-id/E2870D8CE1CCD311BAF50008C71EDE8E01F74757@MAIL_EXCHANGE

 · 

reply

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: SHenshall@westcountrypublications.co.uk, carolyn@greatpacific.com.au
  Subject: Re: weird duplicate data problem
  In-Reply-To: <E2870D8CE1CCD311BAF50008C71EDE8E01F74757@MAIL_EXCHANGE>

* 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