Skip site navigation (1) Skip section navigation (2)

Bug #529: UPDATE fails after an index is changed

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #529: UPDATE fails after an index is changed
Date: 2001-12-04 00:12:11
Message-ID: 200112040012.fB40CBb33940@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Paul Smith (paul(at)cnt(dot)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 that gets 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


Responses

pgsql-bugs by date

Next:From: Hiroshi InoueDate: 2001-12-04 00:34:37
Subject: Re: case sensititvity bug in foreign keys on cygwin
Previous:From: Tom LaneDate: 2001-12-03 18:32:15
Subject: Re: case sensititvity bug in foreign keys on cygwin

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group