Re: proposal - queryid can be used as filter for auto_explain

From: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal - queryid can be used as filter for auto_explain
Date: 2026-04-15 06:37:48
Message-ID: CAKZiRmyt1nuaoxH=P+kQhXqa=5oKo3wO1tgzYSMyvKkMVj68BQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 13, 2026 at 11:02 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> Hi,
>
> On Mon, Apr 13, 2026 at 06:46:24AM +0200, Pavel Stehule wrote:
> >
> > I have to investigate strange behaviour of some specific query. One
> > possibility is non stability of plan. This is a bigger server with a bigger
> > load, and I am a little bit afraid to use auto_explain for all queries.
> >
> > Currently auto_explain doesn't support it, but it can be practical if we
> > can specify a list of queryid as a filter of auto_explain.
> >
> > What do you think about this idea?
>
> +1. I don't think it's something that will be useful very often, but when it's
> going to be useful it would be *extremely* convenient to have.

+1 too.

The only doubt would be: if that's new GUC, then this is list of queryIDs,
right? So do you plan also logging the queryid from auto_explain directly or
one should have %Q in log_line_prefix?

-J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message SATYANARAYANA NARLAPURAM 2026-04-15 06:44:23 [PATCH] Fix WAIT FOR LSN standby_write/standby_flush for archive recovery cases
Previous Message Ashutosh Sharma 2026-04-15 06:30:16 Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication