pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Zhihong Zhang <zhihong@gmail.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Indexing on JSONB field not working
Date: Fri, 3 Jan 2020 10:29:04 -0500
Message-ID: <BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com> (raw)
In-Reply-To: <CAMkU=1wt4Aj9mHyzUXwo3W14xhsdowSxne9ygUFa=Pz=OPnE9g@mail.gmail.com>
References: <0cf001d5b77f$bfe47e10$3fad7a30$@gmail.com>
	<20191220223005.f6w4ff4kdbgtanpz@development>
	<E3D6070E-72E0-4FE5-9E30-D114530F383F@gmail.com>
	<20191221114003.yo56lv3o6thdvxtn@development>
	<21855.1576943356@sss.pgh.pa.us>
	<0AA828F3-5BA5-48CD-B229-8351ACB308D3@gmail.com>
	<167501d5bcdb$13854b20$3a8fe160$@gmail.com>
	<11610.1577468732@sss.pgh.pa.us>
	<202A204F-FE4D-414A-ABD0-B7773A0C7316@gmail.com>
	<CAMkU=1y+D8SyZ+MOQAsJN_4HRm5QaLWFgKe2MyXbkbz0d5fmrA@mail.gmail.com>
	<CE20A918-FDF4-4D43-A969-6CBB70B69164@gmail.com>
	<CAMkU=1waicvb_FODcbJeZ8sO4EqTu7wZX4rQKu88AKxoCy97Zw@mail.gmail.com>
	<A69DA80B-B5A4-4594-8178-55FB5761B386@gmail.com>
	<39B1D245-31C9-407E-8136-514890B92CBA@gmail.com>
	<CAMkU=1wt4Aj9mHyzUXwo3W14xhsdowSxne9ygUFa=Pz=OPnE9g@mail.gmail.com>



> On Jan 3, 2020, at 8:54 AM, Jeff Janes <jeff.janes@gmail.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

view thread (43+ messages)

Message-ID: <BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com>
Permalink:  ../BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com/
Also on:    postgresql.org/message-id/BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: zhihong@gmail.com, jeff.janes@gmail.com, tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com
  Subject: Re: Indexing on JSONB field not working
  In-Reply-To: <BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com>
  References: <0cf001d5b77f$bfe47e10$3fad7a30$@gmail.com> <20191220223005.f6w4ff4kdbgtanpz@development> <E3D6070E-72E0-4FE5-9E30-D114530F383F@gmail.com> <20191221114003.yo56lv3o6thdvxtn@development> <21855.1576943356@sss.pgh.pa.us> <0AA828F3-5BA5-48CD-B229-8351ACB308D3@gmail.com> <167501d5bcdb$13854b20$3a8fe160$@gmail.com> <11610.1577468732@sss.pgh.pa.us> <202A204F-FE4D-414A-ABD0-B7773A0C7316@gmail.com> <CAMkU=1y+D8SyZ+MOQAsJN_4HRm5QaLWFgKe2MyXbkbz0d5fmrA@mail.gmail.com> <CE20A918-FDF4-4D43-A969-6CBB70B69164@gmail.com> <CAMkU=1waicvb_FODcbJeZ8sO4EqTu7wZX4rQKu88AKxoCy97Zw@mail.gmail.com> <A69DA80B-B5A4-4594-8178-55FB5761B386@gmail.com> <39B1D245-31C9-407E-8136-514890B92CBA@gmail.com> <CAMkU=1wt4Aj9mHyzUXwo3W14xhsdowSxne9ygUFa=Pz=OPnE9g@mail.gmail.com> <BB32C709-8342-4920-BE99-5FA4BF32122E@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox