Comments on: PostgreSQL: Script to find Index Size and Index Usage Statistics https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/ BIGData | NoSQL | MSSQL | MySQL | PostgreSQL Wed, 18 Mar 2020 13:11:48 +0000 hourly 1 https://wordpress.org/?v=7.0.4 By: Bassel https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/#comment-8161 Wed, 18 Mar 2020 13:11:48 +0000 https://www.dbrnd.com/?p=3840#comment-8161 Great efforts and really appreciated.

I need to know something. The indexes with total number of scan ‘0’, it will be better if I delete them ?

]]> By: Anvesh Patel https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/#comment-6614 Wed, 22 Aug 2018 20:02:38 +0000 https://www.dbrnd.com/?p=3840#comment-6614 Yup valid error, give schema name outside only

]]> By: Jay https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/#comment-6613 Wed, 22 Aug 2018 05:56:15 +0000 https://www.dbrnd.com/?p=3840#comment-6613 SELECT
pg_size_pretty(pg_relation_size(quote_ident(t.tablename)::text)) AS table_size
FROM pg_tables t
WHERE t.schemaname=’public’

– For this it is working fine and gives details of public schema But if I change the schema name it says relation “table inside the schema name” does not exist

]]> By: Anvesh Patel https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/#comment-6451 Tue, 15 May 2018 19:42:11 +0000 https://www.dbrnd.com/?p=3840#comment-6451 Use IN condition and give multiple schemas

]]> By: Jo https://www.dbrnd.com/2017/01/postgresql-script-to-find-index-size-index-usage-statistics-of-a-database-pg_stat_all_indexes/#comment-6450 Tue, 15 May 2018 10:12:18 +0000 https://www.dbrnd.com/?p=3840#comment-6450 This does not work while having multiple user defined schemas and while queried on one of the schemas alone.

]]>