On Mon, Dec 20, 2010 at 10:33:26AM -0500, James Cloos wrote: > >>>>> "MG" == Mladen Gogala <mladen.gogala@xxxxxxxxxxx> writes: > > MG> Good time accounting is the most compelling reason for having a wait > MG> event interface, like Oracle. Without the wait event interface, one > MG> cannot really tell where the time is spent, at least not without > MG> profiling the database code, which is not an option for a production > MG> database. > > And how exactly, given that the kernel does not know whether the CPU is > active or waiting on ram, could an application do so? > Exactly. I have only seen this data from hardware emulators. It would be nice to have... :) Ken -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
