From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
To: Lukas Fittl <lukas@fittl.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Procedure calls are not tracked in pg_stat_user_functions / track_functions
Date: Mon, 8 Oct 2018 11:30:09 +0200
Message-ID: <3f2f5cf0-c404-4adc-c1ca-28b1407833f0@2ndquadrant.com> (raw)
In-Reply-To: <6d01afee-2a3b-2871-ef41-d3fcd984b192@2ndquadrant.com>
References: <CAP53Pkx1JxGeXHAd3bV=EU7D2s7kAto3v4gqrDrR4as60k77Tw@mail.gmail.com>
<20181004200715.7cgrxyaxnep3mveu@alap3.anarazel.de>
<6d01afee-2a3b-2871-ef41-d3fcd984b192@2ndquadrant.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, andres@anarazel.de, lukas@fittl.com
Subject: Re: Procedure calls are not tracked in pg_stat_user_functions / track_functions
In-Reply-To: <3f2f5cf0-c404-4adc-c1ca-28b1407833f0@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox