From: | Allan Kamau <kamauallan(at)gmail(dot)com> |
---|---|
To: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Weeding out unused user created database objects, could I use pg_catalog? |
Date: | 2010-02-12 15:10:19 |
Message-ID: | ab1ea6541002120710y6207f32fja4b54a4d03a8ccdb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 12, 2010 at 3:47 PM, Richard Huxton <dev(at)archonet(dot)com> wrote:
> On 12/02/10 12:32, Allan Kamau wrote:
>>
>> If I start with a clean deployment, is there a way I could perhaps
>> query the table(s) in pg_catalog for example to find out the database
>> objects (I have constructed) that have been invoked or used in some
>> way during a complete run of my application. I had a quick look at the
>> pg_catalog but was unable to determine the tables that may contain
>> pieces of this information. If pg_catalog could provide me with this
>> solution, what are the table(s) to query?
>
> Quickest solution might be to use the --list option of pg_restore (you'll
> need -Fc on pg_dump too). That will list everything in the database dump and
> you can just compare the lists.
>
> --
> Richard Huxton
> Archonet Ltd
>
I have the DDL scripts of both the old and the new database objects
mixed together, I am looking for a way to distinguish between them.
The objects accessed at any point during the complete run of the
application are the ones I would like to retain. I have no other way
to distinguish between the useful and the defunct objects.
Therefore I am looking for a solution that contains
"last-accessed-time" data for these objects, especially for the
functions and maybe the triggers.
Allan.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-02-12 15:39:30 | Re: Weeding out unused user created database objects, could I use pg_catalog? |
Previous Message | Tom Lane | 2010-02-12 14:53:51 | Re: pg_dump: SQL command failed |