On Fri, Aug 30, 2024 at 10:32 AM Peter Geoghegan wrote:
> It doesn't make a huge difference in practice, because we'll still end
> the scan once the leaf level is reached. But it matters more when
> array keys are involved, where there might be more than one descent to
> the leaf level. Plus we mi
On Sun, Sep 1, 2024 at 11:44 AM bigbro...@hotmail.com
wrote:
> I have reanalysed the code of function _bt_first. I notice that using a
> multi-attribute index
> if we can't identify the starting boundaries and the following attributes
> markded not required ,
> that means we need start at first
is feature.
Anyway we can fix these issues what we had encountered first.
bigbro...@hotmail.com
From: Peter Geoghegan
Date: 2024-08-30 22:32
To: b ro
CC: pgsql-hackers
Subject: Re: bt Scankey in another contradictory case
On Fri, Aug 30, 2024 at 7:36 AM b ro wrote:
> this is the p
On Fri, Aug 30, 2024 at 7:36 AM b ro wrote:
> this is the patch attachment.
We discussed this recently:
https://www.postgresql.org/message-id/80384.1715458896%40sss.pgh.pa.us
I think that we should do this.
It doesn't make a huge difference in practice, because we'll still end
the scan o
Hi,
this is the patch attachment.
发件人: b ro
发送时间: 2024年8月30日 0:56
收件人: pgsql-hackers
主题: bt Scankey in another contradictory case
Hi,
when i read source code of the part of nbtree, i detected another kind of
contradictory case postgresql has not
Hi,
when i read source code of the part of nbtree, i detected another kind of
contradictory case postgresql has not eliminated
(eg. x >4 and x <3) in the function _bt_preprocess_keys in nbtutils.c. this
cause next unnecessary index scan and qual evaluation.
it seems no one will write SQL like th
