Strange problem with an index. - Mailing list pgsql-bugs

From Blanco, Jose
Subject Strange problem with an index.
Date
Msg-id E0217C87D1BA1043AC897ACFA468CEE6015131F7@ECLUST2-VS3.adsroot.itcs.umich.edu
Whole thread Raw
In response to BUG #3750: Invalid frontend message type 112  ("Christian Ullrich" <chris@chrullrich.net>)
Responses Re: Strange problem with an index.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I have the following table=20=20=20=20=20=20=20=20=20=20

Table "public.authorsort"
  Column  |         Type          | Modifiers=20
----------+-----------------------+-----------
 ordernum | integer               |=20
 handle   | character varying(30) |=20
Indexes: author_handle_idx btree (handle)

As you can tell I have an index on handle.

In my perl script I loop trough series of select statements that look
like this:

Select ordernum from authorsort where handle =3D 'somvevalue';

Well, this was running very slowly, so I droped the index and recreated
it, and then it ran quickly.  I'm running versin 7.3 and I noticed that
in versin 8, the following has been done:

Prevent index corruption when a transaction inserts rows and then aborts
close to the end of a concurrent VACUUM on the same table (Tom)

And we recently added vacumm --full to our system.  Could this be the
reason?

Thanks!
Jose

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #3750: Invalid frontend message type 112
Next
From: Tom Lane
Date:
Subject: Re: Strange problem with an index.