Re: Procedure calls are not tracked in pg_stat_user_functions / track_functions

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Lukas Fittl <lukas(at)fittl(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Procedure calls are not tracked in pg_stat_user_functions / track_functions
Date: 2018-10-08 09:30:09
Message-ID: 3f2f5cf0-c404-4adc-c1ca-28b1407833f0@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/10/2018 14:15, Peter Eisentraut wrote:
> On 04/10/2018 22:07, Andres Freund wrote:
>> On 2018-10-04 12:15:28 -0700, Lukas Fittl wrote:
>>> Was this intentional, or an oversight?
>>>
>>> If welcome, I would be happy to work on a patch. Whilst slightly confusing
>>> in terms of naming, we could just track this together with functions, since
>>> one can always join with pg_proc to determine whether something is a
>>> function or a procedure.
>>
>> Yea, that sounds wrong / not ideal to me. I think we should just fix
>> this, should be easy enough.
>
> Here is a patch.

committed

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Александр Аникин 2018-10-08 09:32:03 Re[2]: Create roles trigger
Previous Message Arthur Zakirov 2018-10-08 09:25:13 Re: Segfault when creating partition with a primary key and sql_drop trigger exists