Re: contrib/pg_stat_statements - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: contrib/pg_stat_statements
Date
Msg-id 20081027175317.ADD9.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: contrib/pg_stat_statements  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
Hannu Krosing <hannu@2ndQuadrant.com> wrote:

> > Martin Pihlak <martin.pihlak@gmail.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




pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: contrib/pg_stat_statements
Next
From: "Ibrar Ahmed"
Date:
Subject: ERRORDATA_STACK_SIZE exceeded (server crash)