From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BRIN de-summarize ranges |
Date: | 2017-03-07 12:46:22 |
Message-ID: | CANP8+jK9+yPZOdzxh6D4xEViyeVTZxuGMfCx8YLjzHzh2POAfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 February 2017 at 12:56, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Here's a small patch to make a BRIN page range unsummarized. This is
> useful if data has been deleted, and the heap pages are now used for
> completely different data.
We currently have a manual interface for summarize new values, so it
makes sense to include a manual interface for desummarize also. Since
this adds desummarize_range it would make sense to expose
summarize_range also.
I'd prefer if we had a way to know when the summary is no longer
useful and to do this automatically, but we'd need more info and
research to work out how to do that, so we can only do it this way at
present.
Other than that the patch looks fairly straightforward, so adding a
few tests will be all we need here.
Plus function docs. I'm on the hook to write brin docs anyway, so no
more needed here.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2017-03-07 12:55:30 | Re: One-shot expanded output in psql using \gx |
Previous Message | Amit Kapila | 2017-03-07 12:42:59 | Re: Small fix to postgresql.conf.sample's comment on max_parallel_workers |