Re: Is it useful to record whether plans are generic or custom? - Mailing list pgsql-hackers

From torikoshia
Subject Re: Is it useful to record whether plans are generic or custom?
Date
Msg-id ffb35c235b5040d6da946ab0bdf06e3b@oss.nttdata.com
Whole thread Raw
In response to Re: Is it useful to record whether plans are generic or custom?  (Masahiro Ikeda <ikedamsh@oss.nttdata.com>)
Responses Re: Is it useful to record whether plans are generic or custom?  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
On 2020-06-08 20:45, Masahiro Ikeda wrote:

> BTW, I found that the dependency between function's comments and
> the modified code is broken at latest patch. Before this is
> committed, please fix it.
> 
> ```
> diff --git a/src/backend/commands/prepare.c 
> b/src/backend/commands/prepare.c
> index 990782e77f..b63d3214df 100644
> --- a/src/backend/commands/prepare.c
> +++ b/src/backend/commands/prepare.c
> @@ -694,7 +694,8 @@ ExplainExecuteQuery(ExecuteStmt *execstmt,
> IntoClause *into, ExplainState *es,
> 
>  /*
>   * This set returning function reads all the prepared statements and
> - * returns a set of (name, statement, prepare_time, param_types, 
> from_sql).
> + * returns a set of (name, statement, prepare_time, param_types, 
> from_sql,
> + * generic_plans, custom_plans, last_plan).
>   */
>  Datum
>  pg_prepared_statement(PG_FUNCTION_ARGS)
> ```

Thanks for reviewing!

I've fixed it.



Regards,

--
Atsushi Torikoshi
Attachment

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Default setting for enable_hashagg_disk
Next
From: Justin Pryzby
Date:
Subject: Re: Default setting for enable_hashagg_disk