From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
---|---|
To: | "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: use AV worker items infrastructure for GIN pending list's cleanup |
Date: | 2021-05-15 06:51:46 |
Message-ID: | 39f4f03b-4b3c-4335-a424-8079cd2f7b99@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 15, 2021, at 08:42, Jaime Casanova wrote:
> A customer here has 20+ GIN indexes in a big heavily used table and
> every time one of the indexes reaches gin_pending_list_limit (because of
> an insert or update) a user feels the impact.
>
> So, currently we have a cronjob running periodically and checking
> pending list sizes to process the index before the limit get fired by an
> user operation. While the index still is processed and locked the fact
> that doesn't happen in the user face make the process less notorious and
> in the mind of users faster.
>
> This will provide the same facility, the process will happen "in the
> background".
Sounds like a great improvement, many thanks.
/Joel
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-05-15 08:09:32 | Re: compute_query_id and pg_stat_statements |
Previous Message | Jaime Casanova | 2021-05-15 06:42:12 | Re: use AV worker items infrastructure for GIN pending list's cleanup |