| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josip Rodin <joy(at)entuzijast(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: simple functions, huge overhead, no cache |
| Date: | 2010-07-12 07:38:49 |
| Message-ID: | AANLkTinRRVR20BEoA5qqjdWtJImW6I82Gkj1xdQ7_eNt@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 12, 2010 at 7:06 AM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> wrote:
> It seems like a profiler, which is designed to filter and organize the
> collected data, and which can be attached only to specific functions that
> you want to know about, might be a better job. As there's already a PL/PgSQL
> debugger, some of the infrastructure required is already present.
There's already a profiler in the same source tree. It just needs to
be given a little love.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josip Rodin | 2010-07-12 07:41:18 | Re: simple functions, huge overhead, no cache |
| Previous Message | Pavel Stehule | 2010-07-12 07:12:41 | Re: simple functions, huge overhead, no cache |