| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeremy Finzel <finzelj(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Aggregate not using BRIN index on timestamp |
| Date: | 2019-08-05 17:27:17 |
| Message-ID: | 20190805172717.GA10185@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2019-08-05 18:34:55 | Re: How to check if a field exists in NEW in trigger |
| Previous Message | Tom Lane | 2019-08-05 15:53:47 | Re: Aggregate not using BRIN index on timestamp |