On Sat, 19 Oct 2024 at 22:55, David G. Johnston
wrote:
>
> With auto_explain you end up producing multiple individual explains, one
> for each top-level query being executed. Each one produced by auto_explain
> which hooks into the point where a top-level query begins execution.
> Running explai
On Sat, 19 Oct 2024 at 23:48, Vijaykumar Jain <
vijaykumarjain.git...@gmail.com> wrote:
>
>
> ok, it makes sense for the reason of having auto_explain. but maybe i did
> ask correctly,
> why do we not have the extended flags in auto_explain , in , explain wrt
> nested_statements, and triggers ...
On Sat, Oct 19, 2024 at 10:43 AM Vijaykumar Jain <
vijaykumarjain.git...@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 o
"David G. Johnston" writes:
> On Sat, Oct 19, 2024 at 10:43 AM Vijaykumar Jain <
> vijaykumarjain.git...@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
On Sat, 19 Oct 2024 at 23:31, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Sat, Oct 19, 2024 at 10:43 AM Vijaykumar Jain <
> > vijaykumarjain.git...@gmail.com> wrote:
> >> i tried to check the code for auto_explain , there is nothing that helps
> >> understand why it was provided as a se
On Sat, Oct 19, 2024 at 10:05 AM Vijaykumar Jain <
vijaykumarjain.git...@gmail.com> wrote:
> Why does auto_explain have extended flags to support nested statements and
> triggers whereas explain does not.
> the objects of concern have the same ownership and access, so it does not
> even sound like
