Re: Index Partition Size Double of its Table Partition?

From: David Mullineux <dmullx(at)gmail(dot)com>
To: Don Seiler <don(at)seiler(dot)us>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index Partition Size Double of its Table Partition?
Date: 2024-10-30 21:59:07
Message-ID: CAGsyd8WXZr5-SaAnf2J7MiJheWfxrWTp9+fFhBgB8z93dPC_Vw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Are you able to cluster the table ? The idea is that rows ordered in the
same way as the index might reduce it's size ?

On Wed, 30 Oct 2024, 16:29 Don Seiler, <don(at)seiler(dot)us> wrote:

> On Wed, Oct 30, 2024 at 11:23 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
>>
>> If a substantial amount of the index was written by CREATE INDEX (and
>> not by retail inserts) then my theory is unlikely to be correct. It
>> could just be that you managed to absorb most inserts in one
>> partition, but not in the other. That's probably possible when there
>> are only relatively small differences in the number of inserts that
>> need to use of the space left behind by fillfactor in each case. In
>> general page splits tend to come in distinct "waves" after CREATE
>> INDEX is run.
>>
>
> What do you mean by "absorb" the inserts?
>
> It sounds like the answer will be "No", but: Would rebuilding the index
> after the month-end (when inserts have stopped on this partition) change
> anything?
>
> Don.
> --
> Don Seiler
> www.seiler.us
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paul Brindusa 2024-10-31 10:36:14 pg_wal folder high disk usage
Previous Message Don Seiler 2024-10-30 16:28:54 Re: Index Partition Size Double of its Table Partition?