From: | Oleg Alexeev <oalexeev(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Addled index |
Date: | 2013-03-15 18:29:53 |
Message-ID: | CAHgtPcVuF977UO2uyBLoy4u+y2V9Crznk5+x42tki6bB5LkcOA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We've faced with strange index problem.
At some moment index became bad and queries does not return any data.
For example, there are two tables - A (id, name) and B (id, name, a_id).
B.a_id is foreign key to A. Both name columns in tables contains identical
values for A.id = B.a_id. A.name column has unique constraint and
additional index by it.
So, in some moment results for queries like [select id from A where name =
'petya'] became empty (row with 'petya' name exist in A).
But query [select a_id from B where name = 'petya'] returns A.id and
[select * from A where id = <found id>] returns row.
This problem can be solved by index recreation only.
How can we avoid such situation?
--
Oleg V Alexeev
E:oalexeev(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-03-15 20:09:31 | Re: big un stacking query - help save me from myself |
Previous Message | Bob Brown | 2013-03-15 18:01:59 | link |