Re: BRIN indexes - TRAP: BadArgument - Mailing list pgsql-hackers

From Greg Stark
Subject Re: BRIN indexes - TRAP: BadArgument
Date
Msg-id CAM-w4HPEzAAX9bqVmpTf2MA8eeKP9LCCMm0m4MAtZZtQsjaQnA@mail.gmail.com
Whole thread Raw
In response to Re: BRIN indexes - TRAP: BadArgument  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Tue, Nov 11, 2014 at 1:04 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
>> It might be clearer ...
>
> Patches welcome :-)

Or perhaps there could still be a single opaque field but have two
optional opclass methods "scaninit" and "rescan" which allow the op
class to set or reset whichever fields inside opaque that need to be
reset.


-- 
greg



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index
Next
From: Robert Haas
Date:
Subject: Re: [v9.5] Custom Plan API