From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: bloat indexes - opinion |
Date: | 2017-02-22 22:46:25 |
Message-ID: | CAMkU=1yHT_ZU98QU4ovnwik8kk4HEJ4mM-R1yzHy_KqE7MBCog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Feb 21, 2017 at 1:44 PM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:
> Hi guys,
>
> I've got a lot of bloat indexes on my 4TB database.
>
> Let's take this example:
>
> Table: seg
> Index: ix_filter_by_tree
> Times_used: 1018082183
> Table_size: 18 GB -- wrong. The table is mostly on pg_toast table. Its
> real size is 2TB
> Index_size: 17 GB
> Num_writes 16245023
> Index definition: CREATE INDEX ix_filter_by_tree ON seg USING btree
> (full_path varchar_pattern_ops) WHERE (full_path IS NOT NULL)
>
>
What is this from? If you think the table size reported should include
toast, then change it to do that, or request the author of whatever-this-is
to make that change.
What indication is there that the index is bloated? If the
meat-and-potatoes of a table is held in toast, then wouldn't you expect the
size of the table and the size of the index to be about the same?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Dylan Luong | 2017-02-22 22:58:10 | Postgres HA |
Previous Message | Rob Brucks | 2017-02-22 22:05:42 | Re: NOTIFY command impact |