Postgres Pro
Downloads
Home   >   mailing lists

Re: GIN pending list clean up exposure to SQL - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: GIN pending list clean up exposure to SQL
Date
Msg-id CAHGQGwGcR_n4=q-NVWpzFpzx1GbJWwpjWCbtvwD0cHShvQNMmw@mail.gmail.com
Whole thread Raw
In response to Re: GIN pending list clean up exposure to SQL  (Jaime Casanova <jaime.casanova@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Sun, Nov 22, 2015 at 1:15 PM, Jaime Casanova
<jaime.casanova@2ndquadrant.com> wrote:
> On 21 November 2015 at 03:54, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
>> On 11/19/15 10:47 AM, Jaime Casanova wrote:
>>>
>>> - only superusers?
>>
>>
>> I would think the owner of the table (index?) should also be able to run
>> this.
>
> agreed, that makes sense

Also the function should ensure that the server is running in
normal mode (not recovery mode) and the specified relation is
NOT other session's temporary table.

I added the similar function into pg_bigm extension
(pg_gin_pending_cleanup function in
https://osdn.jp/projects/pgbigm/scm/git/pg_bigm/blobs/master/bigm_gin.c).
It might help us improve the patch.

Regards,

-- 
Fujii Masao

pgsql-hackers by date:

Previous
From: Ants Aasma
Date:
Subject: Re: Re: Revisiting pg_stat_statements and IN() (Was: Re: pg_stat_statements fingerprinting logic and ArrayExpr)
Next
From: Michael Paquier
Date:
Subject: Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.