Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aKD5y-00036A-Tm for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jan 2016 22:43:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aKD5y-0007Ig-Bl for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jan 2016 22:43:50 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aKD4e-0005pB-7m for pgsql-hackers@postgresql.org; Fri, 15 Jan 2016 22:42:28 +0000 Received: from mimolette.dalibo.net ([212.85.157.144]) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1aKD4b-0002Sq-HH for pgsql-hackers@postgresql.org; Fri, 15 Jan 2016 22:42:27 +0000 Received: from [192.168.0.4] (aur75-1-78-192-238-147.fbxo.proxad.net [78.192.238.147]) by mimolette.dalibo.net (Postfix) with ESMTPSA id 2E4C01F13224; Fri, 15 Jan 2016 23:42:22 +0100 (CET) Subject: Re: GIN pending list clean up exposure to SQL To: Jeff Janes References: <56924D75.7060801@dalibo.com> Cc: Jaime Casanova , pgsql-hackers From: Julien Rouhaud Message-ID: <569975CD.3070103@dalibo.com> Date: Fri, 15 Jan 2016 23:42:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 15/01/2016 22:59, Jeff Janes wrote: > On Sun, Jan 10, 2016 at 4:24 AM, Julien Rouhaud > wrote: >> On 29/12/2015 00:30, Jeff Janes wrote: >>> On Wed, Nov 25, 2015 at 9:29 AM, Jeff Janes wrote: >>>> >>>> I'll prepare a patch for core for the January commitfest, and see if >>>> it flies. If not, there is always the extension to fall back to. >>> >>> Here is an updated patch. I've added type and permission checks, >>> docs, and some regression tests. >>> >> >> I just reviewed it. Patch applies cleanly, everything works as intended, >> including regression tests. >> >> I think the function should be declared as strict. > > OK. I see that brin_summarize_new_values, which I modeled this on, > was recently changed to be strict. So I've changed this the same way. > >> >> Also, there are some trailing whitespaces in the documentation diff. > > Fixed. Thanks! > I also added the DESC to the pg_proc entry, which I somehow > missed before. > Good catch, I also missed it. All looks fine to me, I flag it as ready for committer. -- Julien Rouhaud http://dalibo.com - http://dalibo.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers