| From: | Richard Michael <rmichael(at)edgeofthenet(dot)org> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to observe plan_cache_mode transition from custom to generic plan? |
| Date: | 2021-09-10 12:38:18 |
| Message-ID: | CABR0jETyYzw89GnwGadJOdAuhqcDQr82o2M+dXWtesjSujdy_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 10, 2021 at 10:38 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Thu, 2021-09-09 at 16:51 +0200, Richard Michael wrote:
> > > > 2/ EXPLAIN EXECUTE of prepared statement doesn't show query text, as
> the
> > > > documentation seems to imply. Should it?
> > >
> > > Yes, and it does for me - see below.
> >
> > I do not see the query text in your EXPLAIN EXECUTE output. Perhaps I
> am misusing terminology?
>
> My sloppiness. You are right, it does not show the query text. But no
> EXPLAIN
> shows the query text, right?
>
That seems to be correct, yes.
Somewhat related, I noted in my reply to Tom that `auto_explain` does log
the query text,
and ExplainQueryText() was added to commands/explain.c for just that
purpose. auto_explain is
the only code which uses that function.
Regards,
richard
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gus Spier | 2021-09-10 17:26:46 | Re: Is there any technical reason why "alter table .. set not null" can't use index? |
| Previous Message | Richard Michael | 2021-09-10 12:35:36 | Re: How to observe plan_cache_mode transition from custom to generic plan? |