Tom Lane wrote: > Alvaro Herrera <alvhe...@alvh.no-ip.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
