From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Virendra Kumar <viru_7683(at)yahoo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Kevin Brannen <kbrannen(at)efji(dot)com> |
Subject: | Re: how to slow down parts of Pg |
Date: | 2020-04-22 15:49:54 |
Message-ID: | d65819bc-75a6-171e-a434-0ab692af66f9@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/21/20 7:43 PM, Virendra Kumar wrote:
> Hi Adrian,
>
> Here is test case, basically when autovacuum runs it did release the
> space to disk since it had may be continuous blocks which can be
> released to disk but the space used by index is still being held until I
> ran the reindex on the table (I assume reindex for index would work as
> well). Subsequent insert statement did not utilize the blocks in index
> segment as we can see below so index bloats are still not addressed or
> may be I am doing something wrong:
>
Well I learned something. I replicated your commands on my 12 instance
and got the exact same results. I should have read this:
https://www.postgresql.org/docs/12/routine-reindex.html
before.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | brajmohan saxena | 2020-04-22 18:22:20 | PG based ETL tools |
Previous Message | Kevin Brannen | 2020-04-22 15:19:19 | RE: how to slow down parts of Pg |