| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: brin autosummarization -- autovacuum "work items" |
| Date: | 2017-04-01 18:57:27 |
| Message-ID: | CAMkU=1zYusGOVecdXZyFRd-xJayQpV00w9SXwuSfrTnBW4XtdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 1, 2017 at 10:09 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> Alvaro Herrera wrote:
>
> > I also removed the behavior that on index creation the final partial
> > block range is always summarized. It's pointless.
>
> I just pushed this, without this change, because it breaks
> src/test/modules/brin. I still think it's pointless, but it'd require
> more than one line to change.
>
This is failing for me (and the entire build farm, it looks like).
Cheers,
Jeff
| Attachment | Content-Type | Size |
|---|---|---|
| regression.diffs | application/octet-stream | 648 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-04-01 19:16:30 | Re: BRIN de-summarize ranges |
| Previous Message | Tom Lane | 2017-04-01 17:54:45 | Re: New CORRESPONDING clause design |