| From: | Zhihong Zhang <zhihong(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Indexing on JSONB field not working |
| Date: | 2020-01-03 15:29:04 |
| Message-ID: | BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On Jan 3, 2020, at 8:54 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
> You told us vociferously that ANALYZE was run after the index was created.
>
I did have that problem but can’t reproduce it right now. I am just trying to concentrate on the issues I can reproduce easily.
We have been dealing with the slow query issue for months. The first advice is always to run vacuum/analyze. That didn’t help. I think things changed when I accidentally restarted the server by applying some configuration changes. Now, bouncing the server always brings the stats back, without running ‘analyze’.
We had the same issue on another server. I made a snapshot of the database before I restarted the server. Anything I can capture to help nail the issue?
Thanks!
Zhihong
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-01-03 15:41:21 | BUG #16185: Trigger fires twice and with wrong TG_OP when updating partion key on partitioned table |
| Previous Message | Jeff Janes | 2020-01-03 14:50:33 | Re: BUG #16183: PREPARED STATEMENT slowed down by jit |