From: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com> |
---|---|
To: | Horst Düster <horst(dot)duester(at)sourcepole(dot)ch> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Huge table pg_shdepend |
Date: | 2019-01-21 11:50:27 |
Message-ID: | CAGDYbUOqs5WgyY9YbrsX6ddK+yzTDd+YOEkoQXH-MnXPVLHESg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
It may be, when you perform vacuum full, some of the processes connected to
the same or another database that could be holding on to the pg_shdepend
table?
For reclaim the index size perform the reindex.
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Mon, Jan 21, 2019 at 3:48 PM Horst Düster <horst(dot)duester(at)sourcepole(dot)ch>
wrote:
> Hi
>
> I'm struggling with a huge table pg_shdepend. My database has a size of
> 640MB exclude the size of the system tables. But the real size of the db
> is more than 2GB. The reason is a huge table pg_shdepend with more than
> 32000000 records. PgAdmin3 shows a table size of
> 1885MB and an index size of 1690MB. This looks strange for me, because
> this size is a multiple amount of the db size itself. I believe, that
> there are a lot of rubbish in that table, but I'm not sure.
>
> I had run a vacuum full process, but this didn't help. Could anyone give
> me an advice how to clean the table pg_shdepend or reduce the table size?
>
> Any hit would be appreciated.
>
> Regards
> Horst
>
> --
> Dr. Horst Düster
> Managing Director
> Sourcepole AG - Linux & Open Source Solutions
> Weberstrasse 5, 8004 Zürich, Switzerland
> Tel: +41 (0)44 440 77 11
> Direkt: +41 (0)44 515 67 70
> horst(dot)duester(at)sourcepole(dot)ch http://www.sourcepole.ch
>
> qgiscloud.com - Karten einfach vom Desktop ins Netz
>
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Horst Düster | 2019-01-21 11:53:31 | Re: Huge table pg_shdepend |
Previous Message | Ron | 2019-01-21 11:42:02 | Re: Huge table pg_shdepend |