| From: | Vik Fearing <vik(at)2ndquadrant(dot)fr> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 9.5 new features |
| Date: | 2016-01-23 08:35:40 |
| Message-ID: | 56A33B5C.2060301@2ndquadrant.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/23/2016 04:42 AM, John R Pierce wrote:
> On 1/22/2016 7:13 PM, David Rowley wrote:
>> BRIN can be seen as a form of "automatic partitioning", and I have
>> seen it described as such in documents relating to the BRIN project,
>> so perhaps that description has made its way further afield and that's
>> maybe what your coworker heard about.
>>
>> If you view the inheritance partitioning feature as a method of
>> eliminating scans of partitions which can be proved unneeded at
>> planning time, then BRIN can eliminate blocks from a scan of a single
>> relation (or rather "pages_per_range") during execution time. So I
>> agree with the "automatic partitioning" description.
>
> ok, but it doesn't deal with our use case of needing to bulk delete a 6
I can't really parse the end of that sentence, but you are correct that
BRIN does not help at all with partition dropping. Think of it more as
a Seq Scan optimization.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2016-01-23 08:47:09 | Re: Let's Do the CoC Right |
| Previous Message | John J. Turner | 2016-01-23 04:40:45 | Re: Connecting to SQL Server from Windows using FDW |