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

From Chengxi Sun
Subject Re: Is it useful to record whether plans are generic or custom?
Date
Msg-id 161131474094.8805.3570893985530780135.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Is it useful to record whether plans are generic or custom?  (torikoshia <torikoshia@oss.nttdata.com>)
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  tested, failed
Implements feature:       tested, failed
Spec compliant:           not tested
Documentation:            not tested

Hi Atsushi,

I just run a few test on your latest patch. It works well. I agree with you, I think just tracking generic_calls is
enoughto get the reason of performance change from pg_stat_statements. I mean if you need more detailed information
aboutthe plan and execution of prepared statements, it is better to store this information in a separate view. It seems
morereasonable to me.
 

Regards,

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Identify LWLocks in tracepoints
Next
From: "Tang, Haiying"
Date:
Subject: RE: Parallel Inserts in CREATE TABLE AS