| 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 09:41:28 |
| Message-ID: | 56A34AC8.4090101@2ndquadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/23/2016 10:28 AM, John R Pierce wrote:
> On 1/23/2016 12:35 AM, Vik Fearing wrote:
>>> >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.
>
> yeah, it was supposed to say, bulk delete 6 month old data once a week,
> while the database is still under a full production load of new data.
>
> anyways, yeah, BRIN sounds very cool for very large tables with
> relatively stable data.
I have found it particularly efficient when the BRIN index contains all
columns of the table. Just using it on one or two columns is not a win
over btree.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-01-23 09:55:51 | Re: 9.5 new features |
| Previous Message | George Neuner | 2016-01-23 09:28:42 | Re: long transfer time for binary data |