From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RFC: built-in historical query time profiling |
Date: | 2005-03-23 22:34:46 |
Message-ID: | 15071.1111617286@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> ... We can do
> this by writing programs to periodically parse log files for
> queries and durations, and then centralizing that information
> into a db for analysis, similar to pqa's effort.
That strikes me as exactly what you ought to be doing.
> Suppose there were some sort of system relations like these:
This is going to fall down on exactly the same objections that have been
made to putting the log messages themselves into tables. The worst one
is that a failed transaction would fail to make any entry whatsoever.
There are also performance, locking, and security issues to think about.
(Example: heaven help you if someone decides to VACUUM FULL the log
table --- that would block every other process due to exclusive lock.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2005-03-23 23:11:41 | Re: RFC: built-in historical query time profiling |
Previous Message | Ed L. | 2005-03-23 20:32:05 | RFC: built-in historical query time profiling |