Postgres Pro
Downloads
Home   >   mailing lists

Re: Index corruption / planner issue with one table in my pg 11.6 instance - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Index corruption / planner issue with one table in my pg 11.6 instance
Date
Msg-id CAMkU=1wswC4_z1cXch+ksjYz+z7jDeKKHztD33Q=pSRcGmqvYg@mail.gmail.com
Whole thread Raw
In response to Index corruption / planner issue with one table in my pg 11.6 instance  (Jeremy Finzel <finzelj@gmail.com>)
Responses Re: Index corruption / planner issue with one table in my pg 11.6instance  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view
On Mon, Dec 9, 2019 at 1:00 PM Jeremy Finzel <finzelj@gmail.com> wrote:
I have a table with about 7 million records.  I had a query in which I needed 2 indexes added, one for a created timestamp field another for an id field; both very high cardinality.

First I noticed the query would not use the timestamp index no matter what session config settings I used.  I finally created a temp table copy of the table and verified index is used.  Then I rebuilt the main table with VACUUM FULL and this caused the index to be used.

Were they built with CONCURRENTLY?  Do you have any long-open snapshots?

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: log bind parameter values on error
Next
From: Andres Freund
Date:
Subject: Re: log bind parameter values on error