|From:||Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>|
|To:||Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>|
|Cc:||Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Columns correlation and adaptive query optimization|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Wed, 10 Mar 2021 03:00:25 +0100
Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
> What is being proposed here - an extension suggesting which statistics
> to create (and possibly creating them automatically) is certainly
> useful, but I'm not sure I'd call it "adaptive query optimization". I
> think "adaptive" means the extension directly modifies the estimates
> based on past executions. So I propose calling it maybe "statistics
> advisor" or something like that.
I am also agree with the idea to implement this feature as a new
extension for statistics advisor.
> BTW Why is "qual" in
> static void
> AddMultiColumnStatisticsForQual(void* qual, ExplainState *es)
> declared as "void *"? Shouldn't that be "List *"?
When I tested this extension using TPC-H queries, it raised segmentation
fault in this function. I think the cause would be around this argument.
Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
|Next Message||Fujii Masao||2021-03-19 09:27:10||Re: Wrong statistics for size of XLOG_SWITCH during pg_waldump.|
|Previous Messageemail@example.com||2021-03-19 09:05:13||RE: Parallel Inserts in CREATE TABLE AS|