Re: Changing SQL Inlining Behaviour (or...?) - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Changing SQL Inlining Behaviour (or...?)
Date
Msg-id 20190121232724.kbca4x5f3gqcu5ei@alap3.anarazel.de
Whole thread Raw
In response to Re: Changing SQL Inlining Behaviour (or...?)  (Paul Ramsey <pramsey@cleverelephant.ca>)
Responses Re: Changing SQL Inlining Behaviour (or...?)  (Paul Ramsey <pramsey@cleverelephant.ca>)
List pgsql-hackers
Hi,

On 2019-01-21 15:21:29 -0800, Paul Ramsey wrote:
> As a practical matter, most of the exact-test functions have a
> preamble that checks the bbox, so in the seqscan case having the
> operator along for the ride isn’t any advantage. In any event, if we
> do have exact tests w/o a lossy preamble, we could add that for v12,
> as this renovation won’t be a small one if we go this direction.

How expensive are the bbox checks in comparison to the exact tests? IOW,
how much of a problem is it to potentially do a bbox check twice?

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RelationGetIndexAttrBitmap() small deviation between comment and code
Next
From: Paul Ramsey
Date:
Subject: Re: Changing SQL Inlining Behaviour (or...?)