| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | Jennifer Trey <jennifer(dot)trey(at)gmail(dot)com> |
| Cc: | "Massa, Harald Armin" <chef(at)ghum(dot)de>, Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Now I am back, next thing. Final PGS tuning. |
| Date: | 2009-04-08 16:15:56 |
| Message-ID: | d3ab2ec80904080915q7a6dd181t7da98fc816db05a9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 8, 2009 at 12:05 PM, Jennifer Trey <jennifer(dot)trey(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jennifer Trey | 2009-04-08 16:24:40 | Re: Now I am back, next thing. Final PGS tuning. |
| Previous Message | Steve Crawford | 2009-04-08 16:15:26 | Re: Table has 22 million records, but backup doesn't see them |