Re: stored procedures vs pg_stat_statements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: stored procedures vs pg_stat_statements
Date: 2024-12-23 21:58:13
Message-ID: 1493055.1734991093@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> Can this simply be disabled for stored procedures as a special case? I'm
> hoping this might do something useful that is also safe. Curious if anyone
> has any thoughts on this.

No, I don't think that would help. The restriction on utility
statements would cover CREATE PROCEDURE/FUNCTION, not calls
of those things which is what I suppose you care about.

Do you have pg_stat_statements.track set to "all"? That should
allow statements within stored procedures to be tracked, which
again is what I'm guessing you care about.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2024-12-23 22:18:09 Re: Recovering from detoast-related catcache invalidations
Previous Message Merlin Moncure 2024-12-23 21:31:32 stored procedures vs pg_stat_statements