| From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
| Cc: | Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib/pg_stat_statements |
| Date: | 2008-10-27 09:00:22 |
| Message-ID: | 20081027175317.ADD9.52131E4D@oss.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)2ndQuadrant(dot)com> wrote:
> > Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com> wrote:
> > > we need to be able to also track nested statements.
> >
> > I tried your request, but found it's hard to determine query text
> > where the executing plan comes.
>
> Are you sure you need query _text_ ?
> Why not just aggregate on function OID and reslve OID to text only at
> display stage ?
He wants to track pieces of functions.
Function OID and *positions in the source text* would be needed.
Per-function tracking is already done in pg_stat_user_functions,
that uses function OIDs.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ibrar Ahmed | 2008-10-27 10:49:23 | ERRORDATA_STACK_SIZE exceeded (server crash) |
| Previous Message | Hannu Krosing | 2008-10-27 08:50:33 | Re: contrib/pg_stat_statements |