[check_postgres] Issue with check_postgres bloat check.

[Shaik, Baji]

Hi Team,

May I request you for an update on this. Would I need to use 150% instead
of 50%?

On Fri, Oct 16, 2015 at 10:41 AM, Shaik, Baji <baji.shaik at openscg.com>
wrote:

> Hi Team,
>
> I have configured bloat_check for 50% of the table as WARNING, however
> even if tables is bloated less than the percentage configured, it is
> throwing an alert. If you see below example, ONLY 30% of the table is
> bloated, however still I can see the table in the bloated list with 50% as
> critical threshold.
>
> Kindly let me know if I am missing anything.
>
> bloat_test=# \dt+ t
>                      List of relations
>  Schema | Name | Type  |    Owner     | Size  | Description
> --------+------+-------+--------------+-------+-------------
>  public | t    | table | enterprisedb | 69 MB |
> (1 row)
>
> bloat_test=# \q
> root at ubuntu:/home/bajishaik/check_postgres-2.22.0# ./check_postgres_bloat
> --port=5445 --critical='500%' --db='bloat_test' --dbuser='enterprisedb'
> POSTGRES_BLOAT OK: DB "bloat_test" (port=5445) (db bloat_test) table
> public.t rows:1500001 pages:8850 shouldbe:6608 (1.3X) wasted size:18366464
> (17 MB) | public.t=18366464B
> root at ubuntu:/home/bajishaik/check_postgres-2.22.0#
> root at ubuntu:/home/bajishaik/check_postgres-2.22.0#
> root at ubuntu:/home/bajishaik/check_postgres-2.22.0# ./check_postgres_bloat
> --port=5445 --critical='50%' --db='bloat_test' --dbuser='enterprisedb'
> POSTGRES_BLOAT CRITICAL: DB "bloat_test" (port=5445) (db bloat_test) table
> public.t rows:1500001 pages:8850 shouldbe:6608 (1.3X) wasted size:18366464
> (17 MB) | public.t=18366464B
> root at ubuntu:/home/bajishaik/check_postgres-2.22.0#
>
> --
> Regards,
> Baji Shaik,
> Database Consultant | *OpenSCG*
> Phone: 9922995922 | Email: baji.shaik at openscg.com
>



-- 
Regards,
Baji Shaik,
Database Consultant | *OpenSCG*
Phone: 9922995922 | Email: baji.shaik at openscg.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.endcrypt.com/pipermail/check_postgres/attachments/20151019/a5c2fccd/attachment.html>