Re: contrib/pg_stat_statements

From: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
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 08:50:33
Message-ID: 1225097433.7643.5.camel@huvostro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2008-10-27 at 17:00 +0900, ITAGAKI Takahiro wrote:
> Martin Pihlak <martin(dot)pihlak(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ITAGAKI Takahiro 2008-10-27 09:00:22 Re: contrib/pg_stat_statements
Previous Message Koichi Suzuki 2008-10-27 08:41:21 Re: Making pg_standby compression-friendly