Re: Weird behavior: deleted row still in index?

On 4 Dec 2011, at 12:32, Phoenix Kiula wrote:

> mydb=# delete from stores where id = '20xrrs3';
> DELETE 0
> Time: 0.759 ms

It says it didn't delete any rows.
Since you get a duplicate key violation on inserting a row to that table, there's obviously a row with that id there.
Perhaps there's a DELETE trigger or rule on this table that does something unexpected?

It is indeed a possibility that this is a corrupted index, but that is not something that happens unless more serious matters have been (or are) at hand, like hardware failures.

Alban Hertroys

--
The scale of a problem often equals the size of an ego.