Re: contrib/pg_stat_statements - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: contrib/pg_stat_statements
Date
Msg-id 1225097433.7643.5.camel@huvostro
Whole thread Raw
In response to Re: contrib/pg_stat_statements  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: contrib/pg_stat_statements
List pgsql-hackers
On Mon, 2008-10-27 at 17:00 +0900, ITAGAKI Takahiro wrote:
> Martin Pihlak <martin.pihlak@gmail.com> wrote:
> 
> > ITAGAKI Takahiro wrote:
> > > I'd like to submit pg_stat_statements contrib module
> > > 
> > Nice work! There is one feature I'd like to request -- we need to be able
> > to also track nested statements. This would greatly simplify diagnosing
> > performance problems in complex stored procedures. Perhaps the GUC
> > track_statements could be made an enum - none, top, all?
> 
> 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 ?

----------------
Hannu




pgsql-hackers by date:

Previous
From: "Koichi Suzuki"
Date:
Subject: Re: Making pg_standby compression-friendly
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: contrib/pg_stat_statements