Re: track generic and custom plans in pg_stat_statements - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: track generic and custom plans in pg_stat_statements
Date
Msg-id CAA5RZ0t54uP+O2dGZCoYfzOU_wcT2trVL65GdZB00RiLDs9BCg@mail.gmail.com
Whole thread Raw
In response to Re: track generic and custom plans in pg_stat_statements  (Michael Paquier <michael@paquier.xyz>)
Responses Re: track generic and custom plans in pg_stat_statements
List pgsql-hackers
> Perhaps CachedPlanType is
> misnamed, though, would it be more suited to name that as a sort of
> "origin" or "source" field concept?  We want to know which which
> source we have retrieved a plan that a PlannedStmt refers to.

Hmm, I’m not sure I see this as an improvement. In my opinion,
CachedPlanType is a clear name that describes its purpose.

--
Sami



pgsql-hackers by date:

Previous
From: Hironobu SUZUKI
Date:
Subject: [PATCH] Avoid unnecessary code execution in Instrument.c when TIMING is FALSE
Next
From: Fujii Masao
Date:
Subject: Re: Logical replication launcher did not automatically restart when got SIGKILL