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 Jeremy Finzel
Subject Re: Index corruption / planner issue with one table in my pg 11.6 instance
Date
Msg-id CAMa1XUi9gA6-0rt1rvK8Mi-qE99yK42iEwYwXj42WbgwV_zLEQ@mail.gmail.com
Whole thread Raw
In response to Re: Index corruption / planner issue with one table in my pg 11.6 instance  (Jeremy Finzel <finzelj@gmail.com>)
List pgsql-hackers
Tree view
On Tue, Dec 10, 2019 at 8:25 AM Jeremy Finzel <finzelj@gmail.com> wrote:
Is there a way for me to test this theory?  I tried the following with no change in behavior:
  1. Disable write load to table
  2. Vacuum analyze table (not vac full)
  3. Create index
  4. Explain
Still did not pick up the index.

Just another followup: with no other intervention on our part, after many hours the planner is picking up the index.

I don't quite know what is causing it still, but is this behavior actually desired?  It's pretty inconvenient when trying to build an index for a query need and immediately use it which used to work :).

Thanks,
Jeremy

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Wrong assert in TransactionGroupUpdateXidStatus
Next
From: Tom Lane
Date:
Subject: Re: tuplesort test coverage