| From: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> |
|---|---|
| To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, legrand legrand <legrand_legrand(at)hotmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is it useful to record whether plans are generic or custom? |
| Date: | 2021-01-27 22:56:22 |
| Message-ID: | 8c0f5825-2c0a-f6bf-3b8d-61016caa2ea6@nttcom.co.jp_1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Torikoshi-san,
On 2020/12/04 15:03, torikoshia wrote:
>
> ISTM now that creating pg_stat_statements_xxx views
> both for generic andcustom plans is better than my PoC patch.
>
> And I'm also struggling with the following.
>
> | However, I also began to wonder how effective it would be to just
> | distinguish between generic and custom plans. Custom plans can
> | include all sorts of plans. and thinking cache validation, generic
> | plans can also include various plans.
>
> | Considering this, I'm starting to feel that it would be better to
> | not just keeping whether generic or cutom but the plan itself as
> | discussed in the below thread.
>
>
> Yamada-san,
>
> Do you think it's effective just distinguish between generic
> and custom plans?
Sorry for the super delayed replay.
Ah, it's okay.
It would be better to check both info by using a single view from the
perspective of usability. However, it's okay to divide both information
into two views to use memory effectively.
Regards,
Tatsuro Yamada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuro Yamada | 2021-01-27 23:02:02 | Re: Is it useful to record whether plans are generic or custom? |
| Previous Message | Tatsuro Yamada | 2021-01-27 22:53:18 | Re: Is it useful to record whether plans are generic or custom? |