Re: Aggregate not using BRIN index on timestamp

On 2019-Aug-05, Tom Lane wrote:

> FWIW, I suspect the hard part would be dealing with cases where the
> extremal ranges (according to the index) contain no live tuples
> (according to the query's snapshot).  The btree case handles the
> invisible-tuples problem by continuing a scan started at the index
> endpoint until it finds a visible tuple --- which, in the worst case,
> can take a long time.  It's not obvious to me what you'd do with
> BRIN.

Hmm, yeah, that's a tough problem -- hadn't thought about that.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services