From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_stat_user_functions' notion of user |
Date: | 2010-08-08 12:25:06 |
Message-ID: | 1281270306.24942.0.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On tor, 2010-08-05 at 07:13 -0700, David Fetter wrote:
> On Thu, Aug 05, 2010 at 04:58:32PM +0300, Peter Eisentraut wrote:
> > pg_stat_user_functions has an inconsistent notion of what "user" is.
> > Whereas the other pg_stat_user_* views filter out non-user objects
> > by schema, pg_stat_user_functions checks for language "internal",
> > which does not successfully exclude builtin functions of language
> > SQL. Is there a reason for this inconsistency?
>
> If I had to hazard a guess, it would be that the functionality was
> written over time by different people, not all of whom were using the
> same criteria for coherence.
Would anyone object to changing it to make it more consistent with other
others? And since we're jollily making catalog changes in 9.0 still,
could this also be backpatched?
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-08-08 14:11:52 | Re: Surprising dead_tuple_count from pgstattuple |
Previous Message | Marko Tiikkaja | 2010-08-08 10:45:17 | Re: Proposal / proof of concept: Triggers on VIEWs |