| From: | Andrew Bartley <ambartley(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Redundant database objects. |
| Date: | 2010-07-13 06:07:21 |
| Message-ID: | AANLkTil5ynxcmIu78obTRO4Hmnek0C7GIG4tppJ4HlSb@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks Alexander,
Wish i had thought of that.
I still need some way of finding redundant functions
Thanks again
Andrew
On 13 July 2010 15:38, Alexander Pyhalov <alp(at)rsu(dot)ru> wrote:
> Hello.
> When we moved old projects from postgresql 7.x to 8.4, I just looked at
> modification time for files in base/<dboid>/<toid> . So, I could determine,
> that some databases were inactive (precisely,not updated) for about a year
> and move them to archive...
>
> Andrew Bartley wrote:
>
> Is there an effective way to identify these objects using the stats
>> tables? Something like a last accessed/used or some such column?
>> Any suggestions welcomed.
>> Thanks
>>
>> Andrew Bartley
>> Aimstats Pty Ltd
>>
>>
>
> --
> С уважением,
> Александр Пыхалов,
> системный администратор ЮГИНФО ЮФУ.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andras Fabian | 2010-07-13 06:31:18 | Re: PG_DUMP very slow because of STDOUT ?? |
| Previous Message | tamanna madaan | 2010-07-13 05:54:37 | Re: "attempted to lock invisible tuple" error while update |