| From: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie>, Michael Paquier <michael(at)paquier(dot)xyz>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index corruption / planner issue with one table in my pg 11.6 instance |
| Date: | 2019-12-12 13:52:14 |
| Message-ID: | CAMa1XUi9gA6-0rt1rvK8Mi-qE99yK42iEwYwXj42WbgwV_zLEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 10, 2019 at 8:25 AM Jeremy Finzel <finzelj(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-12-12 14:27:04 | Re: tuplesort test coverage |
| Previous Message | Amit Kapila | 2019-12-12 13:25:50 | Re: Wrong assert in TransactionGroupUpdateXidStatus |