Re: use AV worker items infrastructure for GIN pending list's cleanup

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Euler Taveira <euler(at)eulerto(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: use AV worker items infrastructure for GIN pending list's cleanup
Date: 2021-04-05 14:47:41
Message-ID: 20210405144741.GA2737@ahch-to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 05, 2021 at 10:41:22AM -0300, Euler Taveira wrote:
> On Mon, Apr 5, 2021, at 3:31 AM, Jaime Casanova wrote:
> > When AV worker items where introduced 4 years ago, i was suggested that
> > it could be used for other things like cleaning the pending list of GIN
> > index when it reaches gin_pending_list_limit instead of making user
> > visible operation pay the price.
> >
> > That never happened though. So, here is a little patch for that.
> >
> > Should I add an entry for this on next commitfest?
> +1. It slipped through the cracks along the years. It is even suggested in the
> current docs since the fast update support.
>
> https://www.postgresql.org/docs/current/gin-tips.html
>

Interesting, that comment maybe needs to be rewritten. I would go for
remove completely the first paragraph under gin_pending_list_limit entry

>
> Could you provide a link from the previous discussion?
>

It happened here:
https://www.postgresql.org/message-id/flat/20170301045823.vneqdqkmsd4as4ds%40alvherre.pgsql

--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2021-04-05 14:49:04 RE: Stronger safeguard for archive recovery not to miss data
Previous Message Bharath Rupireddy 2021-04-05 14:35:32 Re: TRUNCATE on foreign table