| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Matheus Martin <matheus(dot)martin(at)voidbridge(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Missing query plan for auto_explain. |
| Date: | 2022-09-02 04:48:57 |
| Message-ID: | 20220902044857.jt4mtwo4djgq56po@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On Thu, Sep 01, 2022 at 08:20:13PM +0100, Matheus Martin wrote:
> We tried running the prepared statement six times as suggested but wasn't
> still able to recreate the original problem.
>
> Perhaps more concerning/relevant is that we have not found any explanation
> to why the explain plan is not being logged by `auto_explain`. Could this
> be a bug? Shall we report it?
Just to be sure, do you get at least some plans logged by auto_explain when
queries are executed by the JDBC application?
Can you try to temporarily lower auto_explain.log_min_duration_statements to
less than 50ms and see what auto_explain sees for the execution time (and
planning time).
Another possibility would be some conflicting locks held. If the conflict
happens during the planning auto_explain still won't be triggered as it's
outside the executor. Also, have you enabled log_lock_waits?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Martin | 2022-09-02 09:58:58 | Re: Missing query plan for auto_explain. |
| Previous Message | Meera Nair | 2022-09-02 04:41:27 | RE: Unable to archive logs in standby server |