Skipping PgStat_FunctionCallUsage for many expressions - Mailing list pgsql-hackers

From Andres Freund
Subject Skipping PgStat_FunctionCallUsage for many expressions
Date
Msg-id 20161126041236.wtmn23zjcfsil6mw@alap3.anarazel.de
Whole thread Raw
Responses Re: Skipping PgStat_FunctionCallUsage for many expressions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

while working on my faster expression evaluation stuff I noticed that a
lot of expression types that call functions don't call the necessary
functions to make track_functions work.

ExecEvalFunc/ExecEvalOper (via ExecMakeFunctionResultNoSets) call
pgstat_init_function_usage/pgstat_end_function_usage, but others like
ExecEvalRowCompare, ExecEvalMinMax, ExecEvalNullIf, ExecEvalDistinct,
ExecEvalScalarArrayOp (and indirectly ExecEvalArrayCoerceExpr) don't.

Similarly InvokeFunctionExecuteHook isn't used very thoroughly.

Are these worth fixing? I suspect yes. If so, do we want to backpatch?

- Andres



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: make default TABLESPACE belong to target table.
Next
From: Tom Lane
Date:
Subject: Re: macaddr 64 bit (EUI-64) datatype support