Re: Patch to avoid gprof profiling overwrites
| От | |
|---|---|
| Тема | Re: Patch to avoid gprof profiling overwrites |
| Дата | |
| Msg-id | 1170284361.6941.115.camel@sakai.localdomain обсуждение исходный текст |
| Ответ на | Patch to avoid gprof profiling overwrites (<korryd@enterprisedb.com>) |
| Ответы |
Re: [pgsql-patches] Patch to avoid gprof profiling overwrites
|
| Список | pgsql-patches |
And the patch is where?
You caught me; guess I'd better make something up fast, huh?
Here it is, thanks.
-- Korry
--------------------------------------------------------------------------- korryd@enterprisedb.com wrote: > It's difficult to profile a backend server process (using gprof) > because each process overwrites any earlier profile as it exits. > > It is especially tricky to nab a useful profile if you happen to have > autovacuum enabled. > > This patch reduces the problem by forcing the backend to 'cd' to a new > directory ($PGDATA/gprof/pid) just before calling exit(), but only if > the backend was compiled with -DLINUX_PROFILE. > > I've tested this with Linux, but not with other host architectures. > > -- Korry > > > > -- > Korry Douglas korryd@enterprisedb.com > EnterpriseDB http://www.enterprisedb.com
-- Korry Douglas korryd@enterprisedb.com EnterpriseDB http://www.enterprisedb.com |
Вложения
В списке pgsql-patches по дате отправления: