Re: RFC: built-in historical query time profiling

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFC: built-in historical query time profiling
Date: 2005-03-23 23:51:25
Message-ID: 200503231651.25871.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday March 23 2005 3:34, Tom Lane wrote:
>
> 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.)

I see your point. The ugliness of log-parsing beckons.

Thanks.
Ed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2005-03-23 23:59:20 Re: WAL: O_DIRECT and multipage-writer
Previous Message Ed L. 2005-03-23 23:35:35 Re: RFC: built-in historical query time profiling