On Thu, Jul 15, 2010 at 1:04 AM, Andrew Bartley wrote:
> Thanks to all that replied,
> I used Joe Conway's suggestion, using grep and an extracted list of tables,
> functions and views form the DB. It worked very well.
>
> I will attach the code I used to this thread once complete.
> Again Thanks
Thanks to all that replied,
I used Joe Conway's suggestion, using grep and an extracted list of tables,
functions and views form the DB. It worked very well.
I will attach the code I used to this thread once complete.
Again Thanks
Andrew Bartley
On 14 July 2010 00:43, Greg Smith wrote:
> An
Andrew Bartley wrote:
It seems that the underlying stats tables are reset on a periodic
basis, can i stop this process? Is it a .conf setting?
Up until PostgreSQL 8.2 there's a setting named
stats_reset_on_server_start that clears everything when the server
stops:
http://www.postgresql.org/
Hello
2010/7/13 Andrew Bartley :
> Thanks Alexander,
> Wish i had thought of that.
> I still need some way of finding redundant functions
> Thanks again
> Andrew
>
I used a function source code injection for this task
see
http://www.postgres.cz/index.php/Injekt%C3%A1%C5%BE_zdrojov%C3%A9ho_k%C3%
On 07/12/2010 11:07 PM, Andrew Bartley wrote:
>
> I still need some way of finding redundant functions
A bit of a blunt instrument, but you could log all statements for a
while, and then grep through the logs using a list of all functions of
interest to see which ones never show up. Be wary of th
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 wrote:
> Hello.
> When we moved old projects from postgresql 7.x to 8.4, I just looked at
> modification time for files in base// .
Hello.
When we moved old projects from postgresql 7.x to 8.4, I just looked at
modification time for files in base// . 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
Thanks Greg,
It seems that the underlying stats tables are reset on a periodic basis, can
i stop this process? Is it a .conf setting? I have had a good look around,
nothing sticks out. If I can stop it, then i could use pg_stat_reset() then
monitor the stat views over an extended period without t
Andrew Bartley wrote:
Unfortunately these views only give me what appears to be a certain
time frame. This does not help all that much. It will give a list of
tables, indexes and sequences that have been used in the time frame,
so that is at least a start.
You can use pg_stat_reset() to set
Thanks Joe,
Unfortunately these views only give me what appears to be a certain time
frame. This does not help all that much. It will give a list of tables,
indexes and sequences that have been used in the time frame, so that is at
least a start.
It would be good if there was a timestamp (last
On 07/12/2010 02:40 PM, Andrew Bartley wrote:
> We have a large number of orphaned or redundant tables, views, and
> functions, due to many years of inadequate source management.
>
> We are running " PostgreSQL 8.3.7 on i486-pc-linux-gnu, compiled by GCC
> gcc-4.3.real (Debian 4.3.2-1.1) 4.3.2 "
Hi all,
Our project has been running for 10 years now.
We have a large number of orphaned or redundant tables, views, and
functions, due to many years of inadequate source management.
We are running " PostgreSQL 8.3.7 on i486-pc-linux-gnu, compiled by GCC
gcc-4.3.real (Debian 4.3.2-1.1) 4.3.2 "
12 matches
Mail list logo
