Re: [doc] adding way to examine the plan type of prepared statements

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [doc] adding way to examine the plan type of prepared statements
Date: 2020-12-28 10:47:39
Message-ID: CAD21AoCq7BRBkUw9QJEHaVTqK_FWJwB_8EvSXueKzd+R2Btt7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Torikoshi-san,

On Thu, Nov 19, 2020 at 3:19 PM torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> wrote:
>
> On 2020-11-18 11:04, torikoshia wrote:
> > Hi,
> >
> >
> > Currently, EXPLAIN is the only way to know whether the plan is generic
> > or custom according to the manual of PREPARE.
> >
> > https://www.postgresql.org/docs/devel/sql-prepare.html
> >
> > After commit d05b172, we can also use pg_prepared_statements view to
> > examine the plan types.
> >
> > How about adding this explanation like the attached patch?
>
> Sorry, but on second thought, since it seems better to add
> the explanation to the current description of pg_prepared_statements,
> I modified the patch.
>

You sent in your patch, v2-0001-add-way-to-examine-plan-type.patch to
pgsql-hackers on Nov 19, but you did not post it to the next
CommitFest[1]. If this was intentional, then you need to take no
action. However, if you want your patch to be reviewed as part of the
upcoming CommitFest, then you need to add it yourself before
2021-01-01 AoE[2]. Thanks for your contributions.

Regards,

[1] https://commitfest.postgresql.org/31/
[2] https://en.wikipedia.org/wiki/Anywhere_on_Earth

--
Masahiko Sawada
EnterpriseDB: https://www.enterprisedb.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-12-28 11:05:49 Re: postgres_fdw - cached connection leaks if the associated user mapping/foreign server is dropped
Previous Message Magnus Hagander 2020-12-28 10:42:03 Re: doc review for v14