Bug #529: UPDATE fails after an index is changed - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #529: UPDATE fails after an index is changed
Date
Msg-id 200112040012.fB40CBb33940@postgresql.org
Whole thread Raw
Responses Re: Bug #529: UPDATE fails after an index is changed
List pgsql-bugs
Paul Smith (paul@cnt.org) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
UPDATE fails after an index is changed

Long Description
I had to drop and re-create an index on a table for a large insert. Then I needed to run an UPDATE on a different table
thatgets its values from the first table. UPDATE fails with this error message:  
'ERROR:  Index 6708054 does not exist'.

Sample Code
update users set office_id = offices.office_id where users.infobase_branchid = offices.infobase_branchid and
users.infobase_perid>= 18140; 

No file was uploaded with this report

pgsql-bugs by date:

Previous
From: "Beerman, Michael B"
Date:
Subject: Re: Bug #525: createlang for plperl fails on Tru64 version 4.0F (v 7.1.3)
Next
From: Hiroshi Inoue
Date:
Subject: Re: case sensititvity bug in foreign keys on cygwin