From: | Ben Bennett <fiji(at)ayup(dot)limey(dot)net> |
---|---|
To: | Tim Holloway <mtsinc(at)southeast(dot)net>, Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it> |
Cc: | PostgreSQL Hackers <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Logging - events supported |
Date: | 1999-10-25 11:39:02 |
Message-ID: | 19991025073902.A31645@ayup.limey.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Not sure if I missed something, but it would be nice to be able to log
performance information such as "query 'XYZ' performed a table scan on
a 3,000,000 row table", "query 'XYZ' took 3000 seconds to complete",
"query 'XYZ' forced a sort of a 4,000,000 row table", etc. where the
thresholds could be set by the administrator. This would allow you to
periodically audit your server to make sure that there were sufficient
indices and that users/programmers were not writing really bad
queries.
Although I am not sure how difficult adding this to the backend is but
I would love to be able to hook a tool onto the logfile and see what
bad queries were being run while I ran an appliation against the
server. This is especially useful if my application allows dynamic
queries.
-ben
From | Date | Subject | |
---|---|---|---|
Next Message | Nguyen, Thuan X | 1999-10-25 13:38:38 | |
Previous Message | Peter Eisentraut | 1999-10-25 08:49:41 | Re: [HACKERS] Re: [PATCHES] COMMENT ON patch |