| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>, 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 13:41:22 |
| Message-ID: | 8e4b20bc-4b76-4787-92f5-db3dba97a790@www.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
> To avoid fluctuations in observed response time, it's desirable to have
> pending-list cleanup occur in the background (i.e., via autovacuum).
Could you provide a link from the previous discussion?
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2021-04-05 13:42:48 | Re: ModifyTable overheads in generic plans |
| Previous Message | Jürgen Purtz | 2021-04-05 13:18:44 | Re: Additional Chapter for Tutorial - arch-dev.sgml |