Re: what's the slowest part in the SQL

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Suya Huang <shuang(at)connexity(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: what's the slowest part in the SQL
Date: 2016-08-10 18:10:34
Message-ID: CAGTBQpb5B3FYdV1M=gHkFZjb2HQQzuEDtDBC92g7eSVg_yHfew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Aug 9, 2016 at 10:46 PM, Suya Huang <shuang(at)connexity(dot)com> wrote:
> Hi Claudio,
>
> Here is the index definition
> "idx_data_3" gin (name gin_trgm_ops), tablespace "tbs_data"
> "idx_data_4" gin (displayname gin_trgm_ops), tablespace "tbs_data"

GIN indexes are quite big, they can be bigger than the data. Check
their size, it's possible that you can't fit data + indexes on those
2GB.

But if prod is going to be bigger, prehaps it's a non-issue for you?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andrey Zhidenkov 2016-08-11 10:46:47 Planner do seq scan on empty master partitioned table
Previous Message Pavel Stehule 2016-08-10 11:39:17 Re: Logging queries using sequential scans