| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM |
| Date: | 2017-11-02 20:11:16 |
| Message-ID: | 20171102201116.n3mhcaacrbzmvmfx@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Tom Lane wrote:
> >> If VACUUM and brin_summarize_new_values both ignore the partial
> >> range, then what else would request this? Can't we just decree
> >> that we don't summarize the partial range, period?
>
> > brin_summarize_range() can do it.
>
> So what would happen if we just don't summarize partial ranges?
Index scan would always have to read all the heap pages for that partial
range. Maybe not a big issue, but when you finish loading a table, it'd
be good to have a mechanism to summarize that partial range ...
Rather than remove the capability, I'd be inclined to make
brin_summarize_new_values summarize the final partial range, and have
VACUUM not do it. Would that be too inconsistent?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-11-02 20:20:19 | Re: [PATCH] Add ALWAYS DEFERRED option for constraints |
| Previous Message | Peter Geoghegan | 2017-11-02 19:51:45 | Re: MERGE SQL Statement for PG11 |