| From: | Ronan Vargas <ronan(dot)vargas(at)gmail(dot)com> |
|---|---|
| To: | Feike Steenbergen <feikesteenbergen(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13838: Problem in a table with integer primary key |
| Date: | 2016-01-06 11:09:24 |
| Message-ID: | CA+qiafyzFMO_gbuyi07nx1SO_iWg7C1jg-YZs2PsTTCAfr8gBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Feike,
It was a corrupt index. We ran "reindex" under CLIENTS table and the
problem was solved.
Thank you very much for help!
Att,
Ronan.
2015-12-29 18:26 GMT-02:00 Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>:
> Could you do an explain analyze of both of these statements? It may help
> in understanding the issue.
>
> If it's a primary key, I assume the first query to be using the primary
> key index.
> The second variant will probably be a sequential scan on the table.
>
> If these give different results, it may be a corrupt index, you could try
> to reindex the specific index or the table, see
> http://www.postgresql.org/docs/9.1/static/sql-reindex.html
>
--
Ronan Lima Vargas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-01-06 15:09:30 | Re: BUG #13847: WARNING: skipping "pg_toast_" --- cannot vacuum indexes, views, or special system tables VACUUM |
| Previous Message | Michael Paquier | 2016-01-06 05:41:32 | pg_regress --help missing description of --bindir |