On Fri, Feb 12, 2010 at 9:13 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Richard Huxton <dev@xxxxxxxxxxxx> writes: >> On 12/02/10 15:10, Allan Kamau wrote: >>> Therefore I am looking for a solution that contains >>> "last-accessed-time" data for these objects, especially for the >>> functions and maybe the triggers. > >> Ah, sorry - misunderstood. There's not any timestamp kept. As you can >> imagine, it would be a cost you'd have to pay every time you accessed an >> object. > >> The best you can do is to turn on statement logging, parse the logs to >> see what objects are used and then keep those and their dependencies. > > Or: remove some objects, run your test case, see if it succeeds. > Repeat as needed. > > regards, tom lane > Thanks Richard and Tom for your suggestions, I already have statement logging (as the application is still in development phase) in CSV format. I will create a table of the same structure as this log file and import the data into the DB, then perform the neccessary queries on this table. Since I am also capturing the duration per statement I will use the opportunity to streamline some of my queries and stored procedures. Allan. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
