MIME-Version: 1.0
References: <CAM+6J96FeJxruxqPcZTxTuanKbZzmy0AUMOzChAr72y4iSd+7g@mail.gmail.com>
 <CAKFQuwYCf42_Gvf3pbyjgYzJ2-adS6j_hBgde+ORck2vXXKO5w@mail.gmail.com> <CAM+6J949waO2r35PDFJ65fy1Anc+oukOOy_CRw4wY65qiNc_2g@mail.gmail.com>
In-Reply-To: <CAM+6J949waO2r35PDFJ65fy1Anc+oukOOy_CRw4wY65qiNc_2g@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Sat, 19 Oct 2024 10:50:01 -0700
Message-ID: <CAKFQuwY0SSLdm7KLmRVouXD_2=60-oOsdXfF56gx9n=bNhvWnw@mail.gmail.com>
Subject: Re: explain vs auto_explain
To: Vijaykumar Jain <vijaykumarjain.github@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000bb15730624d80e49"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwY0SSLdm7KLmRVouXD_2%3D60-oOsdXfF56gx9n%3DbNhvWnw%40mail.gmail.com>
Precedence: bulk

--000000000000bb15730624d80e49
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 19, 2024 at 10:43=E2=80=AFAM Vijaykumar Jain <
vijaykumarjain.github@gmail.com> 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.

--000000000000bb15730624d80e49
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Sat, Oct 19, 2024 at 10:43=E2=80=AFAM Vijaykumar Jain &=
lt;<a href=3D"mailto:vijaykumarjain.github@gmail.com">vijaykumarjain.github=
@gmail.com</a>&gt; wrote:</span></div></div><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"=
ltr"><div dir=3D"ltr">i tried to check the code for auto_explain , there is=
 nothing that helps understand why it was provided as a separate .</div></d=
iv></div></blockquote><div><br></div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif">Probably because output to log was =
easier than reworking the internals to make output to client happen.</div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helveti=
ca,sans-serif">If you are interested in working on a patch to address your =
use case I say go for it.=C2=A0 Designing the inputs and outputs actually d=
oesn&#39;t seem that challenging, if exceptionally vulnerable to bike-shedd=
ing.=C2=A0 But I imagine the internals are quite a different matter.</div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helveti=
ca,sans-serif">David J.</div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif"><br></div></div></div>

--000000000000bb15730624d80e49--