| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
| Cc: | Lukas Fittl <lukas(at)fittl(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_plan_advice |
| Date: | 2026-03-26 14:37:15 |
| Message-ID: | CA+Tgmob6=9SeuoXiT6S25zT4fNrvVVb8FTbvu_bOyCAjoeOHLQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 26, 2026 at 10:30 AM Matheus Alcantara
<matheusssilv97(at)gmail(dot)com> wrote:
> Adding support for auto_explain to explain(plan_advice, ...) (or any
> other custom explain option from loadable modules) would help or make
> sense here? I have been thinking about this for a while.
I think that some generic support for custom explain options in
auto_explain is a good idea, but if you use that method to collect
advice strings, you're going to have quite a bit of log-filtering work
to do to get anything useful out of it. That might be fine for some
people, and it's certainly better than nothing, but I think eventually
we want a cleaner way. But still, +many for upgrading auto_explain
with this feature.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2026-03-26 14:37:28 | Re: Clean up NamedLWLockTranche stuff |
| Previous Message | Matheus Alcantara | 2026-03-26 14:30:40 | Re: pg_plan_advice |