Re: Proposal: Progressive explain - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Proposal: Progressive explain
Date
Msg-id CA+TgmoY0hj+P68iB_JrVMoEV4mbAKthiY2i36ksgFPfU7i80SQ@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Progressive explain  (Rafael Thofehrn Castro <rafaelthca@gmail.com>)
Responses Re: Proposal: Progressive explain
List pgsql-hackers
On Fri, Mar 28, 2025 at 12:09 PM Rafael Thofehrn Castro
<rafaelthca@gmail.com> wrote:
> As you said, visibility on the non instrumented query plan is already a feature
> of auto_explain.

True, although thinking about it more, they're not being sent to the
same place. auto_explain goes to the log, and this goes to a view.
What about something like this:

progressive_explain = on | off
progressive_explain_inteval = 5s

If progressive_explain is off, then we don't populate the view. If
it's on, then we populate the view during query startup. Every time
the interval elapses, we update it again. If you want to update the
view just once at query startup and not thereafter, you can set
progressive_explain_interval = 0.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: per backend WAL statistics
Next
From: Kirill Reshke
Date:
Subject: Re: Amcheck verification of GiST and GIN