Re: Fix gin index cost estimation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fix gin index cost estimation
Date
Msg-id 4011931.1666707537@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fix gin index cost estimation  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Fix gin index cost estimation  (Ronan Dunklau <ronan.dunklau@aiven.io>)
List pgsql-hackers
Alexander Korotkov <aekorotkov@gmail.com> writes:
> I think Tom's point was that it's wrong to add a separate entry-tree CPU
> cost estimation to another estimation, which tries (very inadequately) to
> estimate the whole scan cost. Instead, I propose writing better estimations
> for both entry-tree CPU cost and data-trees CPU cost and replacing existing
> CPU estimation altogether.

Great idea, if someone is willing to do it ...

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Finnerty, Jim"
Date:
Subject: Re: parse partition strategy string in gram.y
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert