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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Cc: Julien Rouhaud <rjuju123(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-06-16 05:55:47
Message-ID: CAFj8pRAN+ewir9PL1yAY6e2tVN=R=oMmrh0hKRVEDxx+s9aWqA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

st 15. 4. 2026 v 9:39 odesílatel Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
napsal:

>
>
> st 15. 4. 2026 v 8:37 odesílatel Jakub Wartak <
> jakub(dot)wartak(at)enterprisedb(dot)com> napsal:
>
>> 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?
>>
>
> I plan a new GUC with a list of values. I haven't thought about
> implementation yet. I'll send a prototype next week.
>
> Regards
>
> Pavel
>
>
Today I finished the patch.

Regards

Pavel

>
>
>
>> -J.
>>
>

Attachment Content-Type Size
v20260616-1-0001-auto_explain.log_queryids.patch text/x-patch 9.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ewan Young 2026-06-16 06:07:14 Re: [PATCH] pg_restore_extended_stats() can store an MCV list that cannot be read back
Previous Message solai v 2026-06-16 05:52:26 Re: Preserve index stats during ALTER TABLE ... TYPE ...