pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Zhihong Zhang <zhihong@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Indexing on JSONB field not working
Date: Sat, 28 Dec 2019 20:40:24 -0500
Message-ID: <23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@gmail.com> (raw)
In-Reply-To: <20191228235604.g75ymd7dvc5nwxgt@development>
References: <20191228235604.g75ymd7dvc5nwxgt@development>

The stats was sent in a previous email. Let me know if you can’t find it.

Zhihong

> On Dec 28, 2019, at 6:56 PM, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
> 
> On Sat, Dec 28, 2019 at 02:59:07PM -0500, Zhihong Zhang wrote:
>>> 
>>> Only one of your indexes is over an expression.  The index over a
>>> plain column will never have stats, as column stats are stored with
>>> the table, not the index.
>>> 
>> 
>> Oh. That explains it. I tweaked a few server parameters, wonder if that
>> made the difference. I changed,
>> 
>> pg_stat_statements.track:    ALL    
>> 
>> track_activity_query_size: 2048
>> 
>> Now we have stats, can anyone see why the index is not used?
>> 
> 
> I don't follow. Neither of these configuration options should affect
> which indexes have stats. The expression index should have stats no
> matter how these two GUCs are set.
> 
> But once again, you're making claims without actually showing us the
> data. How do you know we have stats now? Show us pg_stats data and
> the explain plans.
> 
> 
> regards
> 
> -- 
> Tomas Vondra                  http://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services 





view thread (43+ messages)  latest in thread

Message-ID: <23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@gmail.com>
Permalink:  ../23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@gmail.com/
Also on:    postgresql.org/message-id/23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@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, tomas.vondra@2ndquadrant.com, jeff.janes@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Indexing on JSONB field not working
  In-Reply-To: <23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@gmail.com>
  References: <20191228235604.g75ymd7dvc5nwxgt@development> <23FF633F-FFF8-4ABE-BCE6-4FF1E1772A26@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