Re: BUG #13838: Problem in a table with integer primary key - Mailing list pgsql-bugs

From Ronan Vargas
Subject Re: BUG #13838: Problem in a table with integer primary key
Date
Msg-id CA+qiafyzFMO_gbuyi07nx1SO_iWg7C1jg-YZs2PsTTCAfr8gBA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13838: Problem in a table with integer primary key  (Feike Steenbergen <feikesteenbergen@gmail.com>)
List 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@gmail.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

pgsql-bugs by date:

Previous
From: Paul Hester
Date:
Subject: Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts
Next
From: Andres Freund
Date:
Subject: Re: BUG #13846: INSERT ON CONFLICT consumes sequencers on conflicts