| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: massive update on gin index |
| Date: | 2022-09-14 20:20:08 |
| Message-ID: | CAB-JLwZeSdiRJkGMFEzpdkN97XbRbYr5G2ntAGzYmAjtRjihog@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Em qua., 14 de set. de 2022 às 16:55, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:
> GIN does have a "pending list" of insertions not yet pushed into the main
> index structure, and search performance will suffer if that gets too
> bloated. I don't recall much about how to control that, but I think
> vacuuming the table will serve to empty the pending list. Also see
>
>
> https://www.postgresql.org/docs/current/gin-implementation.html#GIN-FAST-UPDATE
>
> regards, tom lane
>
Correct, if I want use that index immediately with same performance I have
to call
select pg_catalog.gin_clean_pending_list('idxphones');
Or wait next autovacuum.
thanks
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mladen Gogala | 2022-09-15 01:57:11 | Re: Is it possible to stop sessions killing eachother when they all authorize as the same role? |
| Previous Message | Tom Lane | 2022-09-14 19:55:50 | Re: massive update on gin index |