Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists - Mailing list pgsql-general

From Jeff Janes
Subject Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists
Date
Msg-id CAMkU=1yA8GoAghtQBBEoD1dRDoTRpLOsyhW5hZRtPWMuZB_TqA@mail.gmail.com
Whole thread Raw
In response to Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists  (otar shavadze <oshavadze@gmail.com>)
List pgsql-general
On Tue, Nov 8, 2016 at 12:27 PM, otar shavadze <oshavadze@gmail.com> wrote:

p.s. In "pg_stats" really many values (long lists in "most_common_vals", "most_common_freqs") and in another columns
Which one columns should I show you? All?

most_common_elems.  Is it empty, or is it not empty?  If not empty, does it contain the specific values you used in your queries?

Cheers,

Jeff

pgsql-general by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Re: which work memory parameter is used for what?
Next
From: Tom Lane
Date:
Subject: Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists