| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Andy Yoder <ayoder(at)airfacts(dot)com> |
| Cc: | Allan Kamau <kamauallan(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tool for determining field usage of database tables |
| Date: | 2010-02-25 20:13:05 |
| Message-ID: | dcc563d11002251213p5afde7bfi66d7cc9ac59f21ed@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 25, 2010 at 12:56 PM, Andy Yoder <ayoder(at)airfacts(dot)com> wrote:
> Thanks Allan for the input - I guess I didn't specify enough details. I am looking for some type of tool/report that is already done. We have nearly 1000 tables, over 300 functions to look at a little over a day to provide the answers (all without dropping any other tasks, of course). I had considered the trigger idea, and may end of doing it anyway and just working later, but thought I would check for a "ready-made" solution first.
Nothing as fine grained as per field, but there are the
pg_stat_user_tables and pg_stat_user_indexes
type system tables, which will show how much individual tables and
indexes are getting used.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-25 22:24:47 | Re: After each row trigger NOT seeing data changes? |
| Previous Message | Andy Yoder | 2010-02-25 19:56:57 | Re: Tool for determining field usage of database tables |