Re: GIN pending list clean up exposure to SQL

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>
Cc: Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN pending list clean up exposure to SQL
Date: 2016-01-15 21:59:02
Message-ID: CAMkU=1w0z86n=+N1yFfKx4-wrO1m6M9XvEFBhV6TQmV4sK1waw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 10, 2016 at 4:24 AM, Julien Rouhaud
<julien(dot)rouhaud(at)dalibo(dot)com> wrote:
> On 29/12/2015 00:30, Jeff Janes wrote:
>> On Wed, Nov 25, 2015 at 9:29 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> 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. I also added the DESC to the pg_proc entry, which I somehow
missed before.

Thanks,

Jeff

Attachment Content-Type Size
gin_clean_pending_user_v003.patch application/octet-stream 8.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Constantin S. Pan 2016-01-15 22:38:39 Proposal: speeding up GIN build with parallel workers
Previous Message Jeff Janes 2016-01-15 21:07:39 Re: Fuzzy substring searching with the pg_trgm extension