Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: otar shavadze <oshavadze(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists
Date: 2016-11-09 04:19:12
Message-ID: CAMkU=1yA8GoAghtQBBEoD1dRDoTRpLOsyhW5hZRtPWMuZB_TqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Nov 8, 2016 at 12:27 PM, otar shavadze <oshavadze(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-11-09 04:35:48 Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists
Previous Message Andreas Joseph Krogh 2016-11-09 02:45:36 Re: which work memory parameter is used for what?