From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] Using contrib modules in check (Re: pgsql: Fix BRIN to use SnapshotAny during summarization) |
Date: | 2015-08-12 18:52:42 |
Message-ID: | 20150812185242.GL3040@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> However, we did learn something valuable from the fact that all the
> -DCLOBBER_CACHE_ALWAYS critters failed on it: per my earlier message,
> brin_page_items() is unsafe against a relcache flush on the index.
> I'll put that on the 9.5 open items list.
>
> (If I were tasked with fixing it, I'd be tempted to rewrite it to do
> all the work in one call and return a tuplestore; the alternative
> seems to be to try to keep the index open across multiple calls,
> which would be a mess.)
Here's a patch doing that.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
brin-page-items.patch | text/x-diff | 10.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-08-12 19:08:08 | Re: [COMMITTERS] pgsql: Close some holes in BRIN page assignment |
Previous Message | Alvaro Herrera | 2015-08-12 17:21:35 | pgsql: Close some holes in BRIN page assignment |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-08-12 18:57:48 | Re: Raising our compiler requirements for 9.6 |
Previous Message | Qingqing Zhou | 2015-08-12 18:48:06 | Re: fix oversight converting buf_id to Buffer |