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
