Re: Issue in _bt_getrootheight

On Fri, Jul 21, 2023 at 10:42 AM Tom Lane wrote: > > Gurjeet Singh writes: > > Please see attached the patch that does this. Let me know if this patch > > helps. > > I don't like this patch one bit, because it adds a lot of overhead > (i.e., an extra index_open/close cycle for every btree index

Re: Issue in _bt_getrootheight

Gurjeet Singh writes: > Please see attached the patch that does this. Let me know if this patch helps. I don't like this patch one bit, because it adds a lot of overhead (i.e., an extra index_open/close cycle for every btree index in every query) to support a tiny minority use-case. How come we

Re: Issue in _bt_getrootheight

On Tue, Jul 11, 2023 at 9:35 AM Ahmed Ibrahim wrote: > > We have been working on the pg_adviser extension whose goal is to suggest > indexes by creating virtual/hypothetical indexes and see how it affects the > query cost. > > The hypothetical index shouldn't take any space on the disk

Issue in _bt_getrootheight

Hi everyone, We have been working on the pg_adviser extension whose goal is to suggest indexes by creating virtual/hypothetical indexes and see how it affects the query cost. The hypothetical index shouldn't take any space on the disk (allocates 0