Re: Now I am back, next thing. Final PGS tuning. - Mailing list pgsql-general

From Scott Mead
Subject Re: Now I am back, next thing. Final PGS tuning.
Date
Msg-id d3ab2ec80904080915q7a6dd181t7da98fc816db05a9@mail.gmail.com
Whole thread Raw
In response to Re: Now I am back, next thing. Final PGS tuning.  (Jennifer Trey <jennifer.trey@gmail.com>)
Responses Re: Now I am back, next thing. Final PGS tuning.
List pgsql-general


On Wed, Apr 8, 2009 at 12:05 PM, Jennifer Trey <jennifer.trey@gmail.com> wrote:
max_connections = 150 # A comprimise :)

Scott, you mentioned :


You can also use the pg_stat_all_indexes table to look at index scans
vs. tuples being read, this can sometimes hint at index 'bloat'. I
would also recommend pg_stattuple which has a pg_statindex function
for looking at index fragmentation.

From where can I see these stats ? Is there any graphic tool?

   From pgAdmin, you could:

   select * from pg_stat_all_indexes;

  You will see this system view in pgAdmin by:

    database +
        Catalogs +
          PostgreSQL (pg_catalog) +
            Views +

    You should be able to see the structure there.


--Scott


pgsql-general by date:

Previous
From: Steve Crawford
Date:
Subject: Re: Table has 22 million records, but backup doesn't see them
Next
From: Jennifer Trey
Date:
Subject: Re: Now I am back, next thing. Final PGS tuning.