Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)

From: Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)
Date: 1999-05-05 07:54:26
Message-ID: 14127.63721.577146.694904@blanc.aeccom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dirk Lutzebaeck writes:
> Tom Lane writes:
> > Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> writes:
> > > cs=> select envelope from recipient where envelope=510349;
> > > [ returns a tuple that obviously fails the WHERE condition ]
> >
> > Yipes. Do you have an index on the envelope field, and if so is
> > it being used for this query? (Use EXPLAIN to check.) My guess
> > is that the index is corrupted. Dropping and recreating the index
> > would probably set things right.
>
> Yes, thanks, recreating the index cures the problem.

Here is some more info: the automatic vacuum tonight gave the
following errors:

vacuum analyze;
NOTICE: Index recipient_oid_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_addr_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_mem_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_env_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_oid_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_addr_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_mem_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
NOTICE: Index recipient_env_index: NUMBER OF INDEX' TUPLES (1474) IS NOT THE SAME AS HEAP' (1473)
VACUUM

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Massimo Dal Zotto 1999-05-05 08:11:53 new patches
Previous Message Dirk Lutzebaeck 1999-05-05 07:30:35 Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)