Search Postgresql Archives

Re: Recording insert, updates, and deletes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 11, 2007 at 11:46:17AM +0100, Andy Dale wrote:
> If the stats collector is 'lossy ' i will not be able to use it, can anyone
> confirm that it is ? So maybe my best option is to write a simple trigger
> that just increments a counter (value in a separate table) after an
> insert/update/delete and then add this trigger to each table i want to
> record the stats for.  Would this new approach work (i.e. be "lossless") ?

Yes, the stats collector is designed so that if the server is very
busy, it sacrifices accuracy for speed. It's designed to be minimal
impact so that it can be turned on without slowing down your system.

You on the other hand want accuracy over speed, and so the stats
collector is not what you want. Some triggers will do it fine.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog@xxxxxxxxx>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment: signature.asc
Description: Digital signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux