Re: [HACKERS] Surjective functional indexes - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: [HACKERS] Surjective functional indexes
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: [HACKERS] Surjective functional indexes  (Michael Paquier <[email protected]>)
Responses Re: [HACKERS] Surjective functional indexes
List pgsql-hackers

On 15.12.2017 01:21, Michael Paquier wrote:
> On Fri, Dec 15, 2017 at 6:15 AM, Alvaro Herrera <[email protected]> wrote:
>> Konstantin Knizhnik wrote:
>>> If you still thing that additional 16 bytes per relation in statistic is too
>>> high overhead, then I will also remove autotune.
>> I think it's pretty clear that these additional bytes are excessive.
> The bar to add new fields in PgStat_TableCounts in very high, and one
> attempt to tackle its scaling problems with many relations is here by
> Horiguchi-san:
> https://www.postgresql.org/message-id/[email protected]
> His patch may be worth a look if you need more fields for your
> feature. So it seems to me that the patch as currently presented has
> close to zero chance to be committed as long as you keep your changes
> to pgstat.c.


Ok, looks like everybody think that autotune based on statistic is bad idea.
Attached please find patch without autotune.

-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


Attachment

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: autoprewarm is fogetting to register a tranche.
Next
From: Aleksander Alekseev
Date:
Subject: Re: GSoC 2018