| From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>, khan Affan <bawag773(at)gmail(dot)com>, "Wong, Kam Fook (TR Technology)" <kamfook(dot)wong(at)thomsonreuters(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to detect if a postgresql gin index is bloated |
| Date: | 2024-07-26 05:21:15 |
| Message-ID: | CAGeimVp73_NxBjFZtJ623qAt20TsuxVe0Rv_f4nQKiD4783dtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Wong,
Could you check the size of the table and Index both and see whether index
size is disproportionately larger than the size of the table ? If yes then
adopt the smarter way suggested in above response by Laurenz Albe
Regards,
Ikram
On Fri, Jul 26, 2024 at 9:58 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Thu, 2024-07-25 at 23:01 -0400, Keith Fiske wrote:
> > Any more insight on how to use those two options to actually calculate
> GIN bloat?
> > From what I could tell pgstattuple didn't provide anything that could be
> used.
> > I hadn't looked further into the other yet, but if you know how to do
> that already
> > that info would be great.
>
> I don't think that there is anything smarter than to create a new index
> with the
> same definition and see if it is much smaller than the original index...
>
> Yours,
> Laurenz Albe
>
>
>
--
Muhammad Ikram
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wasim Devale | 2024-07-26 06:14:22 | Re: Queries are failing on standby server |
| Previous Message | Laurenz Albe | 2024-07-26 05:08:11 | Re: Queries are failing on standby server |