| From: | Jim Nasby <Jim(at)Nasby(dot)net> |
|---|---|
| To: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
| Cc: | James Cloos <cloos(at)jhcloos(dot)com>, Royce Ausburn <royce(at)inomial(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: CPU bound |
| Date: | 2011-01-02 21:57:01 |
| Message-ID: | 5509F55C-FA66-4813-89C3-B2E62F6E8F49@Nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Dec 20, 2010, at 12:47 AM, Mladen Gogala wrote:
> Good time accounting is the most compelling reason for having a wait event interface, like Oracle. Without the wait event interface, one cannot really tell where the time is spent, at least not without profiling the database code, which is not an option for a production database.
Out of curiosity, have you tried using the information that Postgres exposes to dtrace? I suspect it comes close to what you can get directly out of Oracle...
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marc.hsiao | 2011-01-03 02:01:38 | Re: How to turn autovacuum prevent wrap around run faster? |
| Previous Message | Jim Nasby | 2011-01-02 21:00:57 | Re: encourging bitmap AND |