public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Vijaykumar Jain <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: explain vs auto_explain
Date: Sat, 19 Oct 2024 10:50:01 -0700
Message-ID: <CAKFQuwY0SSLdm7KLmRVouXD_2=60-oOsdXfF56gx9n=bNhvWnw@mail.gmail.com> (raw)
In-Reply-To: <CAM+6J949waO2r35PDFJ65fy1Anc+oukOOy_CRw4wY65qiNc_2g@mail.gmail.com>
References: <CAM+6J96FeJxruxqPcZTxTuanKbZzmy0AUMOzChAr72y4iSd+7g@mail.gmail.com>
<CAKFQuwYCf42_Gvf3pbyjgYzJ2-adS6j_hBgde+ORck2vXXKO5w@mail.gmail.com>
<CAM+6J949waO2r35PDFJ65fy1Anc+oukOOy_CRw4wY65qiNc_2g@mail.gmail.com>
On Sat, Oct 19, 2024 at 10:43 AM Vijaykumar Jain <
[email protected]> wrote:
> i tried to check the code for auto_explain , there is nothing that helps
> understand why it was provided as a separate .
>
Probably because output to log was easier than reworking the internals to
make output to client happen.
If you are interested in working on a patch to address your use case I say
go for it. Designing the inputs and outputs actually doesn't seem that
challenging, if exceptionally vulnerable to bike-shedding. But I imagine
the internals are quite a different matter.
David J.
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: explain vs auto_explain
In-Reply-To: <CAKFQuwY0SSLdm7KLmRVouXD_2=60-oOsdXfF56gx9n=bNhvWnw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox