Re: Inquiry/Help with pg_adviser (problem in index_create function for creating indexes)

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Ahmed Ibrahim <ahmed(dot)ibr(dot)hashim(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Gurjeet Singh <gurjeet(at)singh(dot)im>
Subject: Re: Inquiry/Help with pg_adviser (problem in index_create function for creating indexes)
Date: 2023-06-26 05:50:09
Message-ID: bdeacb19-0be5-251c-9edd-e6f1a93dbd8d@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25/06/2023 17:30, Ahmed Ibrahim wrote:
> The full current code (PR is still draft) can be found at
> https://github.com/DrPostgres/pg_adviser/pull/4
> <https://github.com/DrPostgres/pg_adviser/pull/4>
>
> The idea behind what is being done is creating virtual indexes, and
> measuring the query cost after creating those indexes, and see whether
> we will get a better cost or not, and maximize the benefit from those
> choices.
> So far, the project is okay and compiling/working successfully (with
> Postgres 16), but the problem is when creating
> the virtual indexes (with version 16), I give it flag
> /INDEX_CREATE_SKIP_BUILD/ (just like it was with version 8.3 and was
> working)

https://github.com/HypoPG/hypopg might be of interest to you. It also
creates virtual or "hypothetical" indexes.

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ronan Dunklau 2023-06-26 06:38:35 Re: Add GUC to tune glibc's malloc implementation.
Previous Message Drouvot, Bertrand 2023-06-26 05:45:28 Re: Synchronizing slots from primary to standby